First of all my Setup.
We then got an Error on our alex-plugin, because it couldn't handle anything above Groovy 2.5.14.
Failed to execute goal com.alexnederlof:jasperreports-plugin:2.8:jasper (default) on project server: Error while compiling Jasper reports: java.lang.IncompatibleClassChangeError: class net.sf.jasperreports.compilers.JRGroovyCompiler$ClassCollector has interface org.codehaus.groovy.control.CompilationUnit$ClassgenCallback as super class -> [Help 1]
So I decided to force it to use Version 2.5.14
<groupId>com.alexnederlof</groupId> <artifactId>jasperreports-plugin</artifactId> <version>2.8</version> <dependencies> <!-- https://mvnrepository.com/artifact/org.codehaus.groovy/groovy-all --> <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-all</artifactId> <version>2.5.14</version> <type>pom</type> </dependency> </dependencies>
Not a big deal, until a colleague of mine wrote some Testclasses.
In those he compiled the .jrxml-files with java itself an now the big problem comes in place:
Because we declare Groovy in our pom with verison 3.0.7, the JasperReport Dependency updates his initernalt Groovy dependency also to 3.0.7.
But becaus of, Groovy updated an abstract class to an Interface, we now get the same error and maven buildfailure in our java code, because of those tests. Now we are not able to force jasperreports to use a different GroovyVersion and we don't want to use our own ClassLoader to use both Version
Therefore my big question to Jaspersoft:
When can we get an updated Version of Jasperreports which is using a higher GroovyVersion (like 3.0.7)? I've encountered a lot of this problem on other sides and wonder why there isn't a fix to this, since it look like to be an issue for a while now
Looking forward to see a new update coming
Have a nice day :)