fix: add support for non-major Java versions to be used as toolchains #571
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
tharakadesilva
force-pushed
the
fix/568
branch
2 times, most recently
from
0fe13ee to
1325768
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.
Problem
When using GraalVM with non-LTS Java versions (e.g., Java 23), Bazel fails to build Java targets with the error:
This occurs because:
rules_javaonly provides pre-configured toolchains for LTS Java versions (8, 11, 17, 21)rules_graalvmwas only registering runtime toolchains, not compilation toolchainsjavacto compile Java source filesSolution
This PR adds automatic registration of Java compilation toolchains for all GraalVM versions, not just LTS ones.
Closes #568