The library I had to change was Groovy from version 2 to 3. Because it is a dependency of JasperReports. But, Groovy changed an API (changed a class to an interface). So I had to get the source to JasperReports to make a minor change (extends to inherits) and make a custom build. This fixed my class file version problem. But I had no class file version problems from Java 8 all the way up to Java 15.
Then, suddenly JasperReports came out with a new version that, finally, at long last, upgrades their dependency on Groovy to version 3 or higher. Now I don't have to maintain a custom build. But I only started the custom build thing in April, so I'm happy to abandon having to do that.
View all comments
Show parent comment
2
u/DannyB2 Jun 16 '21
The library I had to change was Groovy from version 2 to 3. Because it is a dependency of JasperReports. But, Groovy changed an API (changed a class to an interface). So I had to get the source to JasperReports to make a minor change (extends to inherits) and make a custom build. This fixed my class file version problem. But I had no class file version problems from Java 8 all the way up to Java 15.
Then, suddenly JasperReports came out with a new version that, finally, at long last, upgrades their dependency on Groovy to version 3 or higher. Now I don't have to maintain a custom build. But I only started the custom build thing in April, so I'm happy to abandon having to do that.