Skip to content
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_javac11-v10.1 (with Java 15 toolchain support) #33

Closed
davido opened this issue Oct 8, 2020 · 6 comments
Closed
Assignees
Labels

Comments

@davido
Copy link
Contributor

davido commented Oct 8, 2020

Now, that bazelbuild/bazel#11871 is landed, there should be new release with JDK 15 toolchain support.

Ideally, Bazel would consume this new java_tools per default, so that Bazel users could just select between supported toolchains: 8, 11, 14 and 15.

@davido
Copy link
Contributor Author

davido commented Oct 8, 2020

//Cc @philwo @comius @Jonpez2

@comius comius self-assigned this Oct 9, 2020
@comius comius added the release label Oct 9, 2020
@comius
Copy link
Collaborator

comius commented Oct 9, 2020

There is a failing test for java_tools on linux bazelbuild/bazel#12244

@comius
Copy link
Collaborator

comius commented Oct 19, 2020

Creating release artifacts for rc1: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/149

@comius comius changed the title Release java_tools with Java 15 toolchain support Release: java_tools_javac11-v10.1 (with Java 15 toolchain support) Oct 19, 2020
@comius
Copy link
Collaborator

comius commented Oct 19, 2020

@comius
Copy link
Collaborator

comius commented Oct 19, 2020

All tests green, except for bazelisk on Windows, which seems unrelated.

Published the release: https://github.com/bazelbuild/java_tools/releases/tag/javac11_v10.1

@davido
Copy link
Contributor Author

davido commented Oct 20, 2020

Thanks!

@davido davido closed this as completed Oct 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants