Repository navigation
Clarify why reactive Helidon uses a jlink image - #353
Merged
Merged
Conversation
GraalVM Community and Oracle GraalVM release on Java 25, and there's no sign of a Java 27 release, so saying GraalVM doesn't support Java 27 "yet" was misleading.
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.
The README and reactive demo script said no GraalVM release supports Java 27 "yet." GraalVM Community and Oracle GraalVM have released only on Java 25 since September 2025, so "yet" implied a Java 27 release that may not come. Both now say that Helidon 27 requires Java 27 and GraalVM releases are based on Java 25.