Releases: daust/JasperReportsIntegration
Version 2.11.0 (release: 23.11.2023)
You can see the full list of issues with details in the milestones page.
New features
- #136 Upgrade libraries to JasperReports 6.20.6
Bug fixes
- none
Changed behaviour
- none
Known issues
- Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
- For running the application on Tomcat10, you have to use
jri-2.11.0-jasper-6.20.6-tomcat10.war
instead ofjri.war
.
Version 2.10.1 (release: 17.01.2023)
You can see the full list of issues with details in the milestones page.
It is mainly a maintenance / bugfix release, specifically to support Oracle Weblogic.
New features
- none
Bug fixes
- #123 Constant utl_http.http_version_1_1 causes compiler issues on older Oracle versions
- #126 2 versions of Log4j dependences
- #118 Deploying jri.war file on Oracle Weblogic Server
Changed behaviour
- none
Known issues
- Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
- For running the application on Tomcat10, you have to use
jri-2.10.1-jasper-6.20.0-tomcat10.war
instead ofjri.war
.
Version 2.10.0 (release: 25.08.2022)
You can see the full list of issues with details in the milestones page.
New features
Bug fixes
- #113 Problem verifying application over HTTPS
Changed behaviour
- none
Deprecated features (still available but will go away eventually)
- none
Obsoleted features (no longer available)
- none
Known issues
- Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
- For running the application on Tomcat10, you have to use
jri-2.10.0-jasper-6.20.0-tomcat10.war
instead ofjri.war
.
Version 2.9.0 (release: 24.08.2022)
You can see the full list of issues with details in the milestones page.
New features
- #101 PDF encryption (with password), see the section on integration and usage for details.
- #109
ipAddressesAllowed
is now available for each data source, not only globally. - #94 Suppressing debug information on the webpage. By default, the application is more secure. All error messages will be suppressed on the webpage. You can still see them in the server logs. And you can activate it in the
application.properties
file. The setting isprintDebugToScreen
in the section[application]
. - #102 Upgrade to jasperreports-libraries 6.19.1
Bug fixes
- #111 Unable to generate .csv file. PDF and xlsx work fine bug. Saving (csv and rtf) files on the server did not work.
- #108 Error deploying on Wildfly application server
- #107 Java 11 compatibility => Error de.oc.jasper.ReportUtilities.(ReportUtilities.java:32). The application has been tested with Java 11.
Changed behaviour
- By default, all error messages will be suppressed. You can activate the setting for development environments through the
application.properties
file. The setting isprintDebugToScreen
in the section[application]
.
Deprecated features (still available but will go away eventually)
- none
Obsoleted features (no longer available)
- none
Known issues
- Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
- For running the application on Tomcat10, you have to use
jri-2.9.0-jasper-6.19.1-tomcat10.war
instead ofjri.war
.
Version 2.8.1 (release: 10.02.2022)
You can see the full list of issues with details in the milestones page.
New features
- none
Bug fixes
- #98 reportsPath: default value and relative paths (../reports or ..\reports) don't work
Changed behaviour
- none
Deprecated features (still available but will go away eventually)
- none
Obsoleted features (no longer available)
- none
Known issues
- Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
- For running the application on Tomcat10, you have to use
jri-2.8.1-jasper-6.18.1-tomcat10.war
instead ofjri.war
.
Version 2.8.0 (release: 09.02.2022)
You can see the full list of issues with details in the milestones page.
New features
- #93 Upgrading log4j 1.x to log4j 2.x (2.17.1)
- #84 Variable for report path
- You can now specify a list of report locations like a search path
- #79
XLIB_HTTP.http_version_1_0
was outdated and is upgraded to 1.1 and implemented as an optional parameter. You can downgrade to 1.0 if this is needed. - #82 Unable to start JRI with tomcat 10. Tomcat changed in release 10 some of the library packages: https://tomcat.apache.org/migration-10.html#Specification_APIs. I will continue to develop using the old packages and create a modified
jri.war
file just for Tomcat10, e.g.jri-2.8.0-jasper-6.18.1-tomcat10.war
. - #70 Upgrade Oracle JDBC libraries to 21.4.0.0.1
- #90 Upgrade spring boot libraries. For security reasons, we include a higher version of the spring boot libraries.
- #80 Upgrade to JasperReportsLibraries 6.18.1
Bug fixes
- #96 Connection pool error when session is killed on server, now reconnects gracefully
- #77 Documentation fix
- #76 Adding XLIB_JASPERREPORTS_IMG to the _remove_user.sql. Fixed the deinstall script.
- #69 Timeout issue when connecting to cloud database. Oracle notification services ons.jar are now removed from the build.
Changed behaviour
- #79 By default, all http requests are now done using
XLIB_HTTP.http_version_1_1
. If this causes issues in your application, you can downgrade to 1.0. It is a new optional parameter inxlib_jasperreports.show_report
andxlib_jasperreports.get_report
Deprecated features (still available but will go away eventually)
- none
Obsoleted features (no longer available)
- none
Known issues
- Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
- For running the application on Tomcat10, you have to use
jri-2.8.0-jasper-6.18.1-tomcat10.war
instead ofjri.war
. - #98 reportsPath: default value and relative paths (../reports or ..\reports) don't work
UPDATE: due to bug #98 the current release is removed. Please use https://github.com/daust/JasperReportsIntegration/releases/tag/v2.8.1 instead
Version 2.7.1 (release: 14.12.2021)
You can see the full list of issues with details in the milestones page.
New features
- none
Bug fixes / Security fixes
- #87 - (CVE-2021-44228) Security warning: New zero-day in the Log4j Java library
Changed behaviour
- none
Deprecated features (still available but will go away eventually)
- none
Obsoleted features (no longer available)
- none
Known issues
- Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
Version 2.7.0 (release: 18.11.2020)
You can see the full list of issues with details in the milestones page.
New features
- #66 - Uptake JasperReports Library 6.16.0
- #26 - Connecting to ATP Database
- #63 - Optimization for developers - adding your own .jar files
Bug fixes
- none
Changed behaviour
- none
Deprecated features (still available but will go away eventually)
- none
Obsoleted features (no longer available)
- none
Known issues
- Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues.
JasperReportsIntegration 2.6.2 (release)
Version 2.6.2 (release: 14.10.2020)
This release contains a number of fixes that came up after the release 2.6.1.
You can see the full list of issues with details in the milestones page.
New features
- #52 - Uptake JasperReports Library 6.15.0
Bug fixes
- #57 - Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986
- #53 - Documentation bugs
- #55 - Barcodes produce classnotfounderror
- #54 - Timeout value from default table not working
- #51 - Batch files on Windows throw error: main class not found
Changed behaviour
- none
Deprecated features (still available but will go away eventually)
- none
Obsoleted features (no longer available)
- none
Known issues
- Please check the current list of open issues: https://github.com/daust/JasperReportsIntegration/issues .
JasperReportsIntegration 2.6.1 (release)
Version 2.6.1 (release: 03.10.2020)
(version 2.6.1 includes all changes from 2.6.0 as well)
With this release, the full source code is published on github and can be used freely. The build process is now implemented using gradle
instead of ant
. Also, it is now a lot easier to upgrade the integration with the newest jasperreports libraries. It can be done just using a configuration parameter and running the gradle build process.
You can see the full list of issues with details in the milestones page.
New features
- #30 - Update the standalone application server to jetty-distribution-9.4.31.v20200723
- #17 - Wrong ojdbc library used causing connection failure
- #30 - Upgrade jasperreports libraries to current version 6.14.0
- #7 - Update documentation
- #40 - APEX 20.1 security bundle (PSE 30990551) rejects response header "Cache-Control: private"
- #2 - Deploying .jrxml and / or .jasper files
- #45 - Update APEX test application (new and updated design for APEX 19.1)
- #44 - Store defaults for url and wallet in configuration table
Bug fixes
- #20 - When using jasper report Integration sessions are not closed propperly bug
- #28 - error connection database on 2.5.0.1
- other changes (2.6.1):
- added missing libraries to the build process and the release:
- jasperreports-chart-customizers-6.14.0.jar
- jasperreports-chart-themes-6.14.0.jar
- jasperreports-fonts-6.14.0.jar
- jasperreports-functions-6.14.0.jar
- removed legacy html documentation, replaced with link to specific version on github, e.g. https://github.com/daust/JasperReportsIntegration/tree/v2.6.1
- added missing libraries to the build process and the release:
Changed behaviour
- none
Known issues
- none