Please or Register to create posts and topics.

Jasperreports 7 and Studio out (surprisingly)

Faster than assumed, TIBCO released the new Version 7, a major release step, of JAsperreports and Jaspersoft Studio:

https://github.com/TIBCOSoftware/jasperreports/tree/7.0.0?tab=readme-ov-file#jasperreports-library-700-change-log

https://community.jaspersoft.com/download-jaspersoft/community-edition/jaspersoft-studio_7.0.0

In many technical topics this step means a big break with old versions. But not least as well as in functionality what you can see quickly i nthe release notes of Jaspersoft Studio:

Change Log (2024-06-21)
=====================
-- Full support for JasperReports® Library 7.0.0
-- Java 17 as the new minimum required environment for the plug-ins
-- JFreeChart Library upgraded to 1.5.4
-- Jersey Library upgraded to 2.39
-- New context menu item "JasperReports > Update JasperReports files" to perform a bulk update of the JRXML and JRTX files to the chosen JRL version
-- Removed Custom Visualization Component plug-in (moved to upcoming Professional)
-- Removed MongoDB plug-in (moved to upcoming Professional)
-- Removed old deprecated HTML component
-- Removed broken Subclipse SVN plug-in
-- Minor and major bug fixes
-- NOTE: the new JRXML 7 model is not compatible with currently existing JasperReports Server versions. So please be sure to properly modify the compatibility settings when needed, for example even configuring the "JasperReports Library Version" option in the "Advanced Settings" of the JasperReports Connection dialog.

For me personally, especially the removal of CVC respectively its movement into the professional version doesn´t mean good...

Be careful! As the last point tells us, newly created JRXML with Jaspersoft Studio 7 may not neccessarily be compatible with the last Community Editions of Jasperreports Server (8.2.0)!

What do you think about that? Please share your thoughts!

Cheers, Thomas

kilian.folger has reacted to this post.
kilian.folger

I have a mixed opinion on this one - with non-backward compatible format of reports templates (JRXML) and migration to a different Java major version - it sounds like Tibco wants to isolate their product from 'Jasper classic' branch. So everyone who want to stay on the recent version of Jasper library - would have to move on products without any source code distributed. A kind of game changer, and the moment where we may see a split into two worlds 'Jasper classic with open ecosystem' and 'Jasper proprietary with modern technologies onboard' - and it's a personal choice of every user, which of these paths to take

kilian.folger has reacted to this post.
kilian.folger

I guess the powers that be have concluded that going for a cash only product is going to be good for them.
Not sure why they would think that.
Especially seeing as the 6.2 Studio and 8.2 Server CE do just fine for a small to medium business.

Interestingly, they didn´t make it yet to upgrade their own commercial environment... The Pro versions of Jasperserver, currently (Marketing)Version 9 are still on Jasperreports 6.21.x.

I would strongly advise against upgrading to a Jasperreports 7.x environment, even if you are using only the library in combination with Jaspersoft Studio.

Indeed, it is not clear yet, if we will upgrade our future forks of Studio and Server to that library version, or how that will exactly look like. At least, that will take some time, as we are currently working mainly on a new Jasperserver Version with some extensions (port to Oracle repository database) and updates (newer JBoss 8 and Jakarta support)

Propably sooner or later we will have to update to Jasperreports 7, to keep compatible to the last and latest open source base from Jaspersoft. But I cannot promise anything when that will be.

For now, we keep all our customers on Jasper Studio 6.20.3 and Jasperreports Server 8.2.0 (aka Jasper Server 6.20.3 ;))

Have nice christmas holidays and a good start in 2025!

Thomas