-
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_javac14-v1.0 release #28
Comments
I'll have a look at this today. |
Buildkite pipeline finished successfully: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/135 I'm about to run these commands now:
|
Done:
@davido Can you take it from here? |
Release uploaded to GitHub, too: https://github.com/bazelbuild/java_tools/releases/tag/javac14_v1.0 |
Thanks, @philwo! |
Thanks again, it works like a charm see updated java 14 toolchain example repository: [1], and updated gerrit change: [2]. [1] https://github.com/davido/bazel_java_toolchain14/blob/master/WORKSPACE#L4 |
Closes bazelbuild#11017. This is the follow-up for PR: [1]. Because of the chicken and the egg problem, it has to be done in three steps: 1. add support for java toolchange JDK 14, done in: [1] 2. publish new java_tools_javac14, kicked off by the pipeline in java_tools repository, in context of: [2] 3. add unit test against released java_tools_javac14 published in step 2, this change Test Plan: $ bazel test //src/test/shell/bazel:bazel_coverage_java_jdk14toolchain_released_test [1] bazelbuild#11514 [2] bazelbuild/java_tools#28
Closes #11017. This is the follow-up for PR: [1]. Because of the chicken and the egg problem, it has to be done in three steps: 1. add support for java toolchange JDK 14, done in: [1] 2. publish new java_tools_javac14, kicked off by the pipeline in java_tools repository, in context of: [2] 3. add unit test against released java_tools_javac14 published in step 2, this change Test Plan: $ bazel test //src/test/shell/bazel:bazel_coverage_java_jdk14toolchain_released_test [1] #11514 [2] bazelbuild/java_tools#28 Closes #11828. PiperOrigin-RevId: 324358602
Closes bazelbuild#11017. This is the follow-up for PR: [1]. Because of the chicken and the egg problem, it has to be done in three steps: 1. add support for java toolchange JDK 14, done in: [1] 2. publish new java_tools_javac14, kicked off by the pipeline in java_tools repository, in context of: [2] 3. add unit test against released java_tools_javac14 published in step 2, this change Test Plan: $ bazel test //src/test/shell/bazel:bazel_coverage_java_jdk14toolchain_released_test [1] bazelbuild#11514 [2] bazelbuild/java_tools#28 Closes bazelbuild#11828. PiperOrigin-RevId: 324358602
Now, that this PR is merged, new
java_tools_javac14
release should be conducted.Cc @philwo.
The text was updated successfully, but these errors were encountered: