-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Bump minimum compiler version to Java 16 #71989
Bump minimum compiler version to Java 16 #71989
Conversation
Pinging @elastic/es-delivery (Team:Delivery) |
Gonna need to get https://github.com/elastic/infra/pull/28480 merged in first since we only have Java 16 on our Linux workers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yay 👍
@elasticmachine update branch |
I think this might also be blocked on the release of 6.2.0 of the Gradle shadow plugin. |
Windows builds are failing due to the lack of JDK 16 on the agents. The ansible playbooks have been updated but there's another issue blocking the new images being build. Have an issue open with infra for this. |
@elasticmachine update branch |
@elasticmachine update branch |
…a-16 # Conflicts: # gradle.properties
…to minimum-compile-java-16
# Conflicts: # .ci/java-versions.properties
This reverts commit bc9521e
Now that we've upgrade to Gradle 7.0 we can bump the minimum compiler version to Java 16 to be in line with the bundled JDK and put us back on a supported version (Java 15 is EOL).
I've also relaxed the JDK requirement for builds run via IntelliJ. The idea here being that the JDK is set by the build, but the build in turn requires a certain JDK. To avoid this awkward chicken/egg situation we just ignore the requirement when running in the IDE. We still fail on the CLI in these scenarios though.