Java 21 migration - #475
Open
VincentCucchietti wants to merge 10 commits into
Open
VincentCucchietti wants to merge 10 commits into
VincentCucchietti wants to merge 10 commits into
Conversation
This file contains hidden or 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
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.
Migrate to Java 21
Mirrors the Java 21 migration already applied to orekit, using the same OpenRewrite
recipe sequence, one recipe per commit, followed by the manual follow-ups needed to
make the build target 21 cleanly.
Recipes:
.get(i)access wherever it sitsnext to other indexed access on the same list, for consistency)
Follow-ups:
hipparchus.compiler.releaseproperty