Grails 2.3.11 and Java 8

[Radu-Stefan Zugravu]

Hi! Because of Oracle ending support for Java 7 I decided that is time for me to upgrade to Java 8. But I am still on Grails 2.3.11. I was wondering, did someone tried Grails 2.3.x with Java 8 or is it only working starting from 2.4.x versions? Thanks!

[Adrian A.]

> I was wondering, did someone tried Grails 2.3.x with Java 8

We tried with several apps, but there are allot of errors, and many plug-ins don't work either.

> or is it only working starting from 2.4.x versions? Thanks!

Really well works only with 2.5.x.

regards,

Adrian A.

[Radu-Stefan Zugravu]

Thanks for your answer. Did you also tried to change the BuildConfig to the following:

grails.project.target.level = 1.7

grails.project.source.level = 1.7

[Radu-Stefan Zugravu]

Can you also give me some examples of plugins not working after you switched to Java 8?

luni, 29 februarie 2016, 11:58:04 UTC+2, Radu-Stefan Zugravu a scris:

[Adrian A.]

> Did you also tried to change the BuildConfig to the following:
> grails.project.target.level = 1.7
> grails.project.source.level = 1.7

We were using with 2.3.11 the above settings already.
However the main problem is not that much in the Language level, but the changes Oracle did to the compiler between minor releases, thus breaking some groovy stuff.

[Adrian A.]

> Can you also give me some examples of plugins not working after you switched to Java 8?

We updated to 2.5.x and also the the latest versions of all plug-ins, and most stuff was working again with Java 8.

Plug-ins that had problems despite the 2.5.x update with Java 8:
 - Resources plug-in, so we switched to AssetPipeline  - this was the biggest code change
 - Searchable: this plug-in breaks the schema-export tasks, so we need to deactivate it when we generate DDLs. There's also no update, since it's discontinued .
 - GORM - Many2Many relationships with Oracle when doing updates (hibernate 3) : the generated/scaffold code works with H2, but not with Oracle, so manual handling is required.


We also tried to jump directly to the 3.x path, but since it's backward incompatible, it requires practically a complete rewrite of applications (the customers won't ever pay for this), and the most important feature of Grails for us: dynamic scaffolding is not working correctly :(.

Regards,

Adrian A.

[Radu-Stefan Zugravu]

We will try to make the switch to 2.5.x. I guess our biggest change will also be the Resources plugin. Thank you very much for all the information.