-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Use the current JDK for testing, but 17 for building #9989
Conversation
Previously we added a PR to run (and compile) under Java 21 #9978 This did not work as expected, as in reality this is configuring under the current JDK, but compilation is being done by Java 17 from the ToolChain set up by the micronaut-build plugin. This PR modifies the test tasks to run on the JDK that is used to start the build. But all compilation will be done via Java 17 from the toolchain.
There is no need for the open hack? |
@dstepanov I'm changing my answer 😉 We do need the open hack, as no matter what I try, I cannot get a kotlin daemon to start with the toolchain JDK Added it in c60ac06 |
I cannot work out how to launch the kotlin daemon on the toolchain jdk
@yawkat do the test changes I had to make make sense? I think with 21 we get an extra executer |
Kudos, SonarCloud Quality Gate passed! |
Previously we added a PR to run (and compile) under Java 21
#9978
This did not work as expected, as in reality this is configuring under the current JDK, but compilation is being done by Java 17 from the ToolChain set up by the micronaut-build plugin.
This PR modifies the test tasks to run on the JDK that is used to start the build.
But all compilation will be done via Java 17 from the toolchain.
I believe this supersedes both #9978 and #9985