-
Notifications
You must be signed in to change notification settings - Fork 8
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
release: java_tools_javac9-v3.0 #13
Labels
Comments
Pipeline for rc1: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/119 |
Creating RC1:
RC1 artifacts and checksums:
|
Bazel CI https://buildkite.com/bazel/bazel-bazel-github-presubmit/builds/3795 finished successfully. |
Releasing RC1:
|
Release artifacts & checksums:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The new release:
@java_tools//:prebuilt_toolchain
which is using all the pre-built tools, including singlejar and ijar, even on remote execution. This toolchain should be used only when host and execution platform are the same, otherwise the binaries will not work on the execution platform.This issue follows the java_tools release process.
release candidates can be found under bazel_java_tools/release_candidates/javac9/v3.0
The text was updated successfully, but these errors were encountered: