-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade java_tools version to javac_11-v2.0 #8498
Closed
Closed
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
hlopko
approved these changes
May 31, 2019
iirina
force-pushed
the
update-java-tools-11-v2.0
branch
from
May 31, 2019 14:04
e0833c6
to
138a37d
Compare
iirina
force-pushed
the
update-java-tools-11-v2.0
branch
from
June 3, 2019 07:20
5d20bab
to
5883f5d
Compare
irengrig
pushed a commit
to irengrig/bazel
that referenced
this pull request
Jun 18, 2019
Upgrade the java tools version in Bazel to `javac_11-v2.0`. This PR fixes reported errors of `missing input file '@remote_java_tools_darwin//:Genclass'` (e.g. bazelbuild/intellij#845). Also update the java_tools version for javac 9 and 10 that are used in tests. New java_tools releases for javac 9 and 10 were required because of new bazel API (`java_toolchain` now has an `jacocorunner` attribute). The detailed release of `javac_11-v2.0` can be found in bazelbuild/java_tools#8. The detailed release of java_tools `javac9-v2.0` and `javac10-v4.0` can be found in bazelbuild/java_tools#10. Closes bazelbuild#8498. PiperOrigin-RevId: 251245301
irengrig
pushed a commit
to irengrig/bazel
that referenced
this pull request
Jul 15, 2019
Upgrade the java tools version in Bazel to `javac_11-v2.0`. This PR fixes reported errors of `missing input file '@remote_java_tools_darwin//:Genclass'` (e.g. bazelbuild/intellij#845). Also update the java_tools version for javac 9 and 10 that are used in tests. New java_tools releases for javac 9 and 10 were required because of new bazel API (`java_toolchain` now has an `jacocorunner` attribute). The detailed release of `javac_11-v2.0` can be found in bazelbuild/java_tools#8. The detailed release of java_tools `javac9-v2.0` and `javac10-v4.0` can be found in bazelbuild/java_tools#10. Closes bazelbuild#8498. PiperOrigin-RevId: 251245301
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.
Upgrade the java tools version in Bazel to
javac_11-v2.0
.This PR fixes reported errors of
missing input file '@remote_java_tools_darwin//:Genclass'
(e.g. bazelbuild/intellij#845).Also update the java_tools version for javac 9 and 10 that are used in tests. New java_tools releases for javac 9 and 10 were required because of new bazel API (
java_toolchain
now has anjacocorunner
attribute).The detailed release of
javac_11-v2.0
can be found in bazelbuild/java_tools#8.The detailed release of java_tools
javac9-v2.0
andjavac10-v4.0
can be found in bazelbuild/java_tools#10.