Allow java 15 and 17 for jvm_target #712
Merged
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.
This seems to fix #711
I've tested some Kotlin targets at my company that depend on java deps and I can successfully build with java 17, but haven't done anything more thorough than that.
Also, what do y'all think about removing the check altogether? Kotlin compiler will fail if an invalid version is provided anyways, and this Bazel-level check doesn't even spare users from that error if they try to use java 17 with a Kotlin compiler that is too old.