release: java_tools_javac11-v1.0

[iirina]

Created artifacts for rc1: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/103

release candidates can be found under bazel_java_tools/release_candidates/javac11/v1.0

Upgrading the java_tools version in bazel is happening in bazelbuild/bazel#8302

[iirina]

proguard was added to the java_tools zip in bazel after rc1 was created, so creating rc2 to include proguard: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/104

• pipeline failed due to a bug in generating the java_tools sources zip and rc2 was not created
• bug fixed by Add java tools dist tests. bazel#8311

[iirina]

Started pipeline for generating rc2: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/106#b282057d-c38e-4b75-8c37-b4dbb6b4b552

pipeline finished successfully at bazel commit hash dbe32ed5bd7476047999e31c0b0f68eb64a3b2ad

[iirina]

creating rc2 in GCS by runnning

src/create_java_tools_release.sh --java_version 11 --java_tools_version 1.0 --rc 2 --release false --commit_hash dbe32ed5bd7476047999e31c0b0f68eb64a3b2ad

[iirina]

Updated java_tools version in bazel to rc2 in bazelbuild/bazel#8302

Buildkite pipeline: https://buildkite.com/bazel/bazel-bazel-github-presubmit/builds/2925 finished successfully.

[iirina]

Releasing rc2:

$ src/create_java_tools_release.sh --java_version 11 --java_tools_version 1.0 --rc 2 --release true

releases/javac11/v1.0/java_tools_javac11_linux-v1.0.zip 3e267c90edd526f426755011b4b273122c1b572d24fc92b0eb0135615905c686
releases/javac11/v1.0/java_tools_javac11_windows-v1.0.zip 39dbc3381907528306129cd4bbac8765c0a703ef4ec4e3a2b92922cdbe80e390
releases/javac11/v1.0/java_tools_javac11_darwin-v1.0.zip 83abe9bbc2ed450410a32368ce18d6ba6713aa0626c7bff0436799108f2a8ce3

Updated java_tools version in bazel to release v1.0 in bazelbuild/bazel#8302