iReport NB Release 3.6.2
November 24, 2009 
--------------------------------------------------------------------------------
The iReport Team is pleased to announce the new iReport release: 3.6.2.
iReport is available as standalone application and as NetBeans plugin for NetBeans IDE 6.x. This version includes several improvements and bug fixes.

New features and changes: 
- Full support for JasperReports 3.6.2 
- New properties to control the chart Vertical Tick Labels 
- New feature to import settings from another iReport installation 
- Support for the new group property "Footer position" and "KeepTogether" 
- Support for $X{} syntax in SQL 
- Support for OrderByExpression in the crosstab bucket 
- Added support for cascading input control (available in Jasperserver Professional 3.7) 
- Several bug fixes 


Download
https://sourceforge.net/projects/ireport/files

iReport plugin for NetBeans
http://plugins.netbeans.org/PluginPortal/faces/PluginDetailPage.jsp?pluginid=4425


Complete changelog
- Fixed Bug 0004394 iReport 3.6.1 options throws NullPointerException
- Fixed Bug 0004399 Reports using Xpath are failling in iReport 3.6.1 but working fine in 3.6.0
- Fixed Bug 0004383 Connection closed after preview
- Fixed Bug 0004428 "No query executer factory class registered" when opening report
- Fixed Bug 0000839 Support for $P!{} parameters in SQL
- New properties to control the chart Vertical Tick Labels
- Several fixes for the TXT exporter
- New feature to import settings from another iReport installation
- Support for Keep Together property of groups
- New settings import wizard
- New Ignore Cell Background export option for XLS/XLSX
- Full support for JasperReports 3.6.2
- Support for OrderByExpression in the crosstab bucket
- Support for the new group property "Footer position" and "KeepTogether"
- Fixed the font extensions exporter
- Fixed editable hyperlink target
- Added support for cascading input control (available in Jasperserver Professional)
- Fixed the import of custom iReport connections from XML
- Fixed a problem setting the JasperReports properties leading in an error using XPath based reports