Jasper Ideas

In this GH issue they claim that Jasper reports library works with Java 17 (with notes about Javaflow and Groovy dependency)

Hope it helps.

The below comments talk about JasperReport Server runtime support for Java 17. But the question is Jasper Library Support for Java 17.

So any specific answer on Jasper Reports Library used in the application?

Any release note, or documentation link, will help to have a clear answer.

Hi Damayanti ,

I will answer to #1 later per mail, but #2 can be helpful for others reading this topic too.

Reason for #2 is being able to keep our product up-to-date and avoid last moment updates at EOF of different products. In our (and many other people too) experience, update software whenever (and reasonably) possible, will not only improve its performances, make you able to use more efficient tools, but also avoid the problems that may occur when migrating from very old major versions to much newer ones (which usually deprecate many features/ecc.. and can cause headaches if you haven't followed the changes of the newer releases ).

Furthermore, Tomcat 8.5 will reach EOF in March 2024, and even if tomcat 9 hasn't yet an EOF date, it will be the next one (likely it will happen in a couple years?). But still, why should Tibco wait the very last moment to release support for jakarta/tomcat 10 ?

In addition to this, we have highly customized our report classes and functionalities to reflect the features of our webapp using jasper report, which we wouldn't want to throw in the bin for such little thing. But since we have scheduled to release our product next year, if the reporting software cannot keep up with our goals, we will have to come back to crystal (in which we have 20+ years of experience. Replicating some of crystal reports' v9 (released in 2002!!) features in jasper reports was not as obvious as it seemed (!) and some are just not there).

These are the reasons why not only me, but the whole community of jasper reports devs would benefit from this "upgrade", and would be grateful if you will be able to put it in the next LTS release (which should happen this month, according to the doc below)

I hope for a positive response!

https://docs.tibco.com/pub/jaspersoft/general/LTS/jaspersoft_LTS_releases.html

Hi Davide, had a few follow up questions

1. Which Jaspersoft product(s) are you currently using?

2. What is the reason to move to Jakarta namespace? Is it related to moving to Tomcat 10 or similar app servers that support Jakarta namespace going forward?

You can respond on if you do not want to reveal this information here

js-product-team@cloud.com

As T v.Rauchhaupt said , support for jakarta should be considered mandatory for the next release! the change in the namespace happened 3 years ago!!! During this period at least 1 LTS of jasper report was released but still without support for jakarta namespace. No support for jakarta namespace in this next release will force us to move to crystal reports

Please consider to support jee 10 as well. Jax-RS is outdated but still needed.

Hi , please let us know ,Is jdk17 with jasper studio good option .Jasper licenced with 17 ?

The below comments talk about JasperReport Server runtime support for Java 17. But the question is Jasper Library Support for Java 17.

So any specific answer on Jasper Reports Library used in the application?

Any release note, or documentation link, will help to have a clear answer.

Finally ! And thanks for letting us know!

Whenever possible, let us know what the ETAs will be.

We have added runtime support for Java 17 in our LTS 8.0.4 recently. You can find details here:

https://community.jaspersoft.com/wiki/installing-jasperreports-server-80x-java-17

We are having conversations internally about Compile time support + Jakarta + Tomcat 10.

"we are looking into this and will keep you updated." on march 30 sounds like a joke on August 30..

Considering switching to Crystal Reports may be a more serious option than it may seem

Let's see if someone from Jaspersoft considers it appropriate to answer the question asked

Crystal Reports already works with jdk 17...

Also, consider this feature too :
https://jaspersoftideas.tibco.com/ideas/JSPR-I-4620

many that use jdk 17 may use tomcat 10 with the newer jakarta namespace.

As Radoslaw points out, this should be top feature

Java 21 is out in weeks, but jasper still fully supports only jdk11 (released in 2018).

Possible that at August 30 this problem has not been already solved ? This problem can't be still "under consideration". Which consideration ?

Hi Damayanti,

Runtime support for Java 17 is sufficient.

As of Release 8.2.0 onwards, JasperReports server has runtime support for Java 17. https://docs.tibco.com/pub/js-jrs/8.2.0/doc/pdf/js-jrs_8.2.0_Platform-Support-Commercial-Edition.pdf

Will this help, or do you need compile time support as well?

Thank you for posting, we are looking into this and will keep you updated.