Jasper Error After Migration

Q&A
1

I installed version 7.5.4 to test and found it to be very good, with many new things that make development easier, but when I imported a process that I had developed in version 7.3.3 to run in version 7.5.4 my jasper report started to give a error that did not occur before:

1. java.util.Date cannot be resolved to a type value = new java.util.Date(); //$JR_EXPR_ID=8$ <------------> 2. java.util.Date cannot be resolved to a type value = new java.util.Date(); //$JR_EXPR_ID=9$ <------------> 3. java.lang.Long cannot be resolved to a type value = ((java.lang.Long)field_quantidade.getValue()); //$JR_EXPR_ID=12$ <------------> 4. java.lang.Long cannot be resolved to a type value = ((java.lang.Long)field_saldo.getValue()); //$JR_EXPR_ID=14$ <------------> 5. java.lang.Long cannot be resolved to a type value = ((java.lang.Long)field_trinta.getValue()); //$JR_EXPR_ID=15$ <------------> 6. java.lang.Long cannot be resolved to a type value = ((java.lang.Long)field_centoOitenta.getValue()); //$JR_EXPR_ID=16$ <------------> 7. java.lang.Long cannot be resolved to a type value = ((java.lang.Long)field_noventa.getValue()); //$JR_EXPR_ID=17$ <------------> 8. java.lang.Long cannot be resolved to a type value = ((java.lang.Long)field_quinze.getValue()); //$JR_EXPR_ID=18$ <------------> 9. java.lang.Long cannot be resolved to a type value = ((java.lang.Long)field_centoOitenta.getValue())/180.0; //$JR_EXPR_ID=19$ <------------> 10. java.lang.Long cannot be resolved to a type value = ((java.lang.Long)field_noventa.getValue())/90.0; //$JR_EXPR_ID=20$ <------------> 11. java.lang.Long cannot be resolved to a type value = ((java.lang.Long)field_trinta.getValue())/30.0; //$JR_EXPR_ID=21$ <------------> 12. java.lang.Long cannot be resolved to a type value = ((java.lang.Long)field_quinze.getValue())/15.0; //$JR_EXPR_ID=22$ <------------>

Has anyone ever gone through something like this and could give me a hint how to solve this?
2

Currently we have a known issue with the Jasper connector and the Java Virtual Machine version 8.
This issue is likely to be fixed in the 7.6.3 release.

Note that the current version of the connector use Jasper Report library in version 5.1.0 (see connector implementation pom.xml). So I would recommend to use iReport Designer 5.1.0 to mitigate the risk of incompatibility.