[java] upgrade to java 21 #1655
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
cyrilou242
force-pushed
the
te-2526-upgrade-to-java-21
branch
from
8ef9765
to
da20a20
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checks:
./mvnw clean installHow to review:
look commit per commit
Ref:
https://nipafx.dev/road-to-21-upgrade/
dropwizard is tested on java 21: dropwizard/dropwizard#8173
https://www.baeldung.com/java-lts-21-new-features
Note 1:
virtual threads may have an impact on the performance/behavior of the system.
this PR does not directly introduce virtual threads usage.
by default, dropwizard does not use virtual threads either: https://www.dropwizard.io/en/stable/manual/configuration.html
the dropwizard virtual threads toggle will be exposed in another PR
Note 2:
java 21 adds support for generational ZGC.
https://openjdk.org/jeps/439
It's likely it will improve the performance of the evaluate endpoint.
This is not in the scope of this PR.