-
-
Notifications
You must be signed in to change notification settings - Fork 952
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
JDK 17 Support / Gradle 7.3.0 #12152
Comments
Grails 5.0.0 depends on Groovy 3.0.7, not 3.0.8. It would be great to wait for Groovy 3.0.10 when it is released. We have runtime issues with Groovy 3.0.8 and 3.0.9.. |
For us Grails 5.0.0 works with Gradle 7.2 and JDK 17 (I believe we have some lucky combination of plugins, which doesn't cause issues). We use gradle But release of 5.0.1 with gradle 7.3 and groovy 3.0.9 out of the box would be highly appreciated. |
@Taack yeah, I realized I had already updated the groovy version prior to 5.0.0 being released. I am getting runtime issues as well with my production app. Are you experiencing something similar and do you expect it to be resolved with Groovy 3.0.10? I have successfully run and built an app using Gradle 7.3 rc2 / Groovy 3.0.8, but in my main production app i have an issue just running my main app with JDK 17 even if it is built with JDK 11. Running the same jar with JDK 11 works find.
|
I diagnosed my issue and found it is do to having multiple I have created the following issue that needs to be resolved in order to support JDK 17 |
@codeconsole I reported one issue GROOVY-10320, it will be resolved with Groovy 3.0.10. I do have another one against Groovy 3.0.8 which cause me headheck, but has been resolved with Groovy 3.0.9 (so I do not report the later). |
This will probably depend on Groovy 4.x support |
I can confirm Grails 5.1.7 working with JDK 17 using Groovy 3.0.11-SNAPSHOT However, the grails cli does not work.
|
The only JDK 17 issues that seem to be remaining are grails cli issues.
|
FYI JDK 17 is version 61 so the CLI is not supporting compiling itself |
This seems like an issue being enforced by the framework grails/grails-spring-security-core#767 |
I ran grails 5.2.2 with jdk 17 by ./gradlew bootRun and it worked normally. |
I can confirm JDK 17 is now working |
Hello, can we announce official support for java 17? |
Has the fix for JDK17 been released into the latest Grails 5.2.5 release? When using Grails 5.2.5 with JDK17, I am unable to build.
This comes from a project created with |
Yes, you are right, Looks this relates to the issue: erdi/webdriver-binaries-gradle-plugin#30
|
Adding this to dependencies fixes the issue
|
Gradle 7.3.0 will soon be released (Currently RC3) and will support JDK 17
JDK is the new LTS and was released in September.
JDK 17 requires asm 9.1 and Groovy 3.0.8 is the first version to support it.
Fortunately, Grails 5.0.0 introduced
groovyVersion
ingradle.properties
and can be updated to Groovy 3.0.8+, so now is the time to start planning for JDK 17 support once Gradle 7.3.0 is released.Current Gradle Computability Matrix
The text was updated successfully, but these errors were encountered: