Skip to content
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

Merged
merged 8 commits into from
Oct 20, 2023

Conversation

timyates
Copy link
Contributor

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

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.
@timyates timyates self-assigned this Oct 17, 2023
@dstepanov
Copy link
Contributor

There is no need for the open hack?

@timyates
Copy link
Contributor Author

timyates commented Oct 17, 2023

No, because all of the compilation is done under 17, but the tests are executed under Java 21 (on the 21 pipelines)

@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

@timyates timyates requested a review from yawkat October 17, 2023 15:23
@timyates
Copy link
Contributor Author

@yawkat do the test changes I had to make make sense? I think with 21 we get an extra executer

@timyates
Copy link
Contributor Author

Java 21 build:

image

Java 17 build:

image

@timyates timyates mentioned this pull request Oct 17, 2023
@sonarcloud
Copy link

sonarcloud bot commented Oct 18, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@sdelamo sdelamo merged commit 2d1dbbd into 4.2.x Oct 20, 2023
16 checks passed
@sdelamo sdelamo deleted the java-21-for-testing branch October 20, 2023 14:33
@sdelamo sdelamo added the relates-to: build label for issues related to the build file or CI label Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
relates-to: build label for issues related to the build file or CI
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants