Roadmap and Background Version 7
Quote from ThoZi on 15. June 2024, 19:20JasperReports Library 7 coming soon!
Work is in progress on a separate branch (release-7.0.0) that will introduce major refactoring of the library, which is needed for the Jakarta Migration. The changes help improving the dependency management by splitting the library into multiple optional artifacts (*.jar files) depending on the functionality they provide. Deprecated code has been removed and the backward compatibility of serialized/compiled *.jasper report template files has been deliberately broken.
More details about the upcoming changes can be found here.
JasperReports Library 7 coming soon!
Work is in progress on a separate branch (release-7.0.0) that will introduce major refactoring of the library, which is needed for the Jakarta Migration. The changes help improving the dependency management by splitting the library into multiple optional artifacts (*.jar files) depending on the functionality they provide. Deprecated code has been removed and the backward compatibility of serialized/compiled *.jasper report template files has been deliberately broken.
More details about the upcoming changes can be found here.
Quote from ThoZi on 27. June 2024, 23:08That went a little faster than expected: Jasperreports 7 is out:
https://community.jaspersoft.com/download-jaspersoft/community-edition/
Find source code and release packages here:
https://github.com/TIBCOSoftware/jasperreports
https://github.com/TIBCOSoftware/jasperreports/releases/tag/7.0.0
The major changes and improvements:
- removal of the Ant build system and replacing it with a Maven build system;
- deprecated code removed;
- breaking backward compatibility of serialized/compiled *.jasper report template files,
mostly because of historical deprecated serialization code removal/cleanup mentioned above
(source *.jrxml report templates need to be recompiled to *.jasper using the new version of
the library);- breaking backward compatibility of source *.jrxml report template files and *.jrtx style
template files by replacing the Apache Commons Digester based parsers with Jackson XML object
serialization. *.jrxml and *.jrtx files created with version 6 or older can no longer be loaded
with version 7 or newer of the library alone. The conversion from the old file formats to the new
file formats and back can be made using Jaspersoft Studio 7 and later versions of it;- extracting various optional extension JAR artifacts from the the core library JAR artifact
to allow the Jakarta Migration of certain of these optional features while also introducing
better third party Maven dependency management of these artifacts;- some Java package names have changed as a consequence of separating functionality into optional JAR artifacts;
- upgraded JFreeChart to version 1.5.4 which no longer has support for 3D charts. Reports having
Pie 3D, Bar 3D and Stacked Bar 3D charts would continue to work, but will be rendered as 2D,
all their 3D effects being ignored;- minor bug fixes and improvements;
That went a little faster than expected: Jasperreports 7 is out:
https://community.jaspersoft.com/download-jaspersoft/community-edition/
Find source code and release packages here:
https://github.com/TIBCOSoftware/jasperreports
https://github.com/TIBCOSoftware/jasperreports/releases/tag/7.0.0
The major changes and improvements:
- removal of the Ant build system and replacing it with a Maven build system;
- deprecated code removed;
- breaking backward compatibility of serialized/compiled *.jasper report template files,
mostly because of historical deprecated serialization code removal/cleanup mentioned above
(source *.jrxml report templates need to be recompiled to *.jasper using the new version of
the library); - breaking backward compatibility of source *.jrxml report template files and *.jrtx style
template files by replacing the Apache Commons Digester based parsers with Jackson XML object
serialization. *.jrxml and *.jrtx files created with version 6 or older can no longer be loaded
with version 7 or newer of the library alone. The conversion from the old file formats to the new
file formats and back can be made using Jaspersoft Studio 7 and later versions of it; - extracting various optional extension JAR artifacts from the the core library JAR artifact
to allow the Jakarta Migration of certain of these optional features while also introducing
better third party Maven dependency management of these artifacts; - some Java package names have changed as a consequence of separating functionality into optional JAR artifacts;
- upgraded JFreeChart to version 1.5.4 which no longer has support for 3D charts. Reports having
Pie 3D, Bar 3D and Stacked Bar 3D charts would continue to work, but will be rendered as 2D,
all their 3D effects being ignored; - minor bug fixes and improvements;
Quote from biffant on 23. September 2024, 19:21I wouldn't worry about JasperReports library 7 for now - unless I had strong reasons to use some functionality which is only available in 7.0.0
I wouldn't worry about JasperReports library 7 for now - unless I had strong reasons to use some functionality which is only available in 7.0.0
Quote from sschotte on 26. February 2025, 8:33Does Jasper Reports libraries 7.x depends on jakarta EE 10 libraries ?
Is there a way to automate the conversion of .jrxml files to the new jasper binary format ? Having lots of report files, it is not an option to manually do this via Jasper Studio.
Is there a way to automate the conversion of the previous format of *.jrxml report template files and *.jrtx style files to the new format ? Having lots of such files, it is not an option to manually do this via Jasper Studio.
Does the new format support everything you could do with the .jrxml files e.g. using expressions referring to specific java classes ?
What is the long term support for the Jasper Reports libraries community edition version 6.x and 7.x ? How long will 6.x be supported (means bugs get fixed)?
Migrating from Jasper Reports libraries 6.x to 7.x requires how much effort ? Are there any documented migration steps we can follow ?
Does Jasper Reports libraries 7.x depends on jakarta EE 10 libraries ?
Is there a way to automate the conversion of .jrxml files to the new jasper binary format ? Having lots of report files, it is not an option to manually do this via Jasper Studio.
Is there a way to automate the conversion of the previous format of *.jrxml report template files and *.jrtx style files to the new format ? Having lots of such files, it is not an option to manually do this via Jasper Studio.
Does the new format support everything you could do with the .jrxml files e.g. using expressions referring to specific java classes ?
What is the long term support for the Jasper Reports libraries community edition version 6.x and 7.x ? How long will 6.x be supported (means bugs get fixed)?
Migrating from Jasper Reports libraries 6.x to 7.x requires how much effort ? Are there any documented migration steps we can follow ?
Quote from ThoZi on 28. February 2025, 0:31Hi sschotte,
I would still not recommend upgrading to JR 7; last week I saw a major bug in Jaspersoft Studio 7... You cannot create or modify variables at all. From my perspective more or less a beta test version.
Another thing is the incompatibility to 6.x and older servers or system environments.
Not at last, the forks of Jasper Tools we are working on will not support JR 7 in the very near future; we wil focus on Java/Jakarta first.
But concretely to your questions:
Does Jasper Reports libraries 7.x depends on jakarta EE 10 libraries
> I will pass the question to my developers; but as long as you do not use a server I do not think that there are any jakarta dependencies
Is there a way to automate the conversion of .jrxml files to the new jasper binary format ? Having lots of report files, it is not an option to manually do this via Jasper Studio.
> It is not a jrxml -> jasper conversion... What has to be done is a converion of your jrxml, jrtx, ... according to the new Version XML specification (what is not compatible to anything anymore as mentioned above)
Does the new format support everything you could do with the .jrxml files e.g. using expressions referring to specific java classes ?
> you can still use java in expressions. So if your java version or third-party libraries do not change, you should not experience any problems from my point of view
What is the long term support for the Jasper Reports libraries community edition version 6.x and 7.x ? How long will 6.x be supported (means bugs get fixed)?
> We are talking about an open source software here... no support. But you can get commercial support here: http://www.biosdb.de
Migrating from Jasper Reports libraries 6.x to 7.x requires how much effort ? Are there any documented migration steps we can follow ?
> depends on your environment
I am sorry that some of my replys are propably vague or not satisfying. But indeed, some of your questions are quite abstract and would propably need further investigation.
However, hopefully it helps a bit.
Thomas
Hi sschotte,
I would still not recommend upgrading to JR 7; last week I saw a major bug in Jaspersoft Studio 7... You cannot create or modify variables at all. From my perspective more or less a beta test version.
Another thing is the incompatibility to 6.x and older servers or system environments.
Not at last, the forks of Jasper Tools we are working on will not support JR 7 in the very near future; we wil focus on Java/Jakarta first.
But concretely to your questions:
Does Jasper Reports libraries 7.x depends on jakarta EE 10 libraries
> I will pass the question to my developers; but as long as you do not use a server I do not think that there are any jakarta dependencies
Is there a way to automate the conversion of .jrxml files to the new jasper binary format ? Having lots of report files, it is not an option to manually do this via Jasper Studio.
> It is not a jrxml -> jasper conversion... What has to be done is a converion of your jrxml, jrtx, ... according to the new Version XML specification (what is not compatible to anything anymore as mentioned above)
Does the new format support everything you could do with the .jrxml files e.g. using expressions referring to specific java classes ?
> you can still use java in expressions. So if your java version or third-party libraries do not change, you should not experience any problems from my point of view
What is the long term support for the Jasper Reports libraries community edition version 6.x and 7.x ? How long will 6.x be supported (means bugs get fixed)?
> We are talking about an open source software here... no support. But you can get commercial support here: http://www.biosdb.de
Migrating from Jasper Reports libraries 6.x to 7.x requires how much effort ? Are there any documented migration steps we can follow ?
> depends on your environment
I am sorry that some of my replys are propably vague or not satisfying. But indeed, some of your questions are quite abstract and would propably need further investigation.
However, hopefully it helps a bit.
Thomas