-
Notifications
You must be signed in to change notification settings - Fork 951
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grails 3.2.11 is incompatible (will not run) with GORM 6.1.3.RELEASE #10693
Comments
This was working in previous versions of Grails (e.g 3.2.8). |
Confirmed just now it was working as recently as 3.2.10. |
The solution is to upgrade to GORM 6.1.5 or alternatively downgrade the Groovy version to 2.4.10 This is a difference in Groovy 2.4.11 and above that we cannot resolve unfortunately |
Upgrading to GORM 6.1.5 isn't bad, so good to know that is an option. I wasn't actually even aware that it was released. However, per https://stackoverflow.com/questions/44635366/is-it-possible-to-have-different-gorm-versions-in-plugins-within-a-grails-3-appl (linked from: grails-plugins/grails-cache-ehcache#25) this will require upgrading every plugin that uses GORM 6.1.3 (and that provides domain objects) to 6.1.5. Even that isn't bad, for plugins that we control. For third party plugins...it's an ongoing challenge. I would greatly appreciate any insight you have on that issue! |
The issue is a binary incompatibility running Groovy code compiled with an older version of Groovy with Groovy version newer than 2.4.11 There really is nothing we can do about it per se. You could report the issue to the Groovy team https://issues.apache.org/jira/projects/GROOVY And see if a new 2.4.x release of Groovy can improve backwards binary compatibility. |
Well, while asking third party plugin owners to upgrade to a newer gorm version isn't the best thing on my to-do list, there aren't all that many (that we use) that provide domain objects at least! And it's good to know that maybe as things calm down on the groovy upgrades this will be less of an issue in the future. Thanks for the quick responses! I'll see if I can narrow this down to something I can report to the Groovy team, but regardless, I'm closing this issue as your suggested fix (upgrade to 6.1.5) is clearly working. For anyone else who stumbles across this, and wonders: I also confirmed that gorm 6.1.5 works fine with grails 3.2.10. I have not tested with older versions than that, but figured it would be good to confirm some backwards compatibility there, in case we can't get everything upgraded right away. Thanks again, Graeme! |
@graemerocher looks like there is no MongoDB GORM for 6.1.5 :( I guess my only option is to "downgrade the Groovy version to 2.4.10", do I have to do it at compile time? I mean recompiling grails-core. Or can it be done at runtime? I have tried exporting CI_GROOVY_VERSION and setting ext.groovyVersion in my build.gradle and also in my setting.gradle without success, so I'm guessing I will have to recompile grails-core. |
I'm also facing similar issue groovy -version logs: |
Steps to Reproduce
I can upload an application if anybody wants (just comment back here) but really, it's just create-app, create-domain-class, change one line, and fail.
Expected Behaviour
Application should start.
Actual Behaviour
Application does not start.
Environment Information
The text was updated successfully, but these errors were encountered: