Make rules_java backwards compatible with Bazel 6.3.0 #210
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
This reverts commit 57a8330.
Move bootstrap_toolchain_type into rules_java. There are no uses outside of rules_java. This fixes compatiblity with Bazel 6.3.0, which doesn't have the definition. Add Bazel 6.3.0 to the CI. Remove a couple of broken targets from toolchains/BUILD. Those were broken becuase old JDKs were removed.
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.
Move bootstrap_toolchain_type into rules_java. There are no uses outside
of rules_java. This fixes compatiblity with Bazel 6.3.0, which doesn't
have the definition.
Add back
_allowlist_function_transition. Older versions of Bazel require it.Add Bazel 6.3.0 to the CI.
Remove a couple of broken targets from toolchains/BUILD. Those were
broken becuase old JDKs were removed.