| commit | e4682f6c6fa5d8d67d667aa6593a34370e689cf5 | [log] [tgz] |
|---|---|---|
| author | keertk <keerthanakumar@google.com> | Mon Apr 24 19:00:22 2023 +0000 |
| committer | GitHub <noreply@github.com> | Mon Apr 24 19:00:22 2023 +0000 |
| tree | 079c7ca80ad1ed027161effc77c9863fac7d1a9b | |
| parent | bb37d0b35563b3f5e608265ad1b9d88183ff3eeb [diff] |
[6.2.0] Update java_tools v12.1 (#18197) * Separate prebuilt darwin java_tools for x86_64 and arm64 This is step 1 of https://github.com/bazelbuild/bazel/issues/17780 Closes #17767. PiperOrigin-RevId: 517115807 Change-Id: If2bb85a8a15fd126ab52e5738e3d9558da813090 * Update rules_java and remove references to "remote_java_tools_darwin" This is the last step of https://github.com/bazelbuild/bazel/issues/17780 This updates rules_java to v5.5.0 for bazel and bazel_tools and cleans up any remaining references to remote_java_tools_darwin, remote_java_tools_test_darwin, and remote_java_tools_darwin_for_testing Closes #17843. PiperOrigin-RevId: 519059189 Change-Id: Ic04f3a2e5cc12e6b7731f6d8a3551553e172e000 * Update java_tools v12.1 https://github.com/bazelbuild/java_tools/issues/69 Closes #18097. PiperOrigin-RevId: 526116409 Change-Id: I4f31046d7e5b149c5035b0ede0699d74685a1eb8 --------- Co-authored-by: hvd <hvadehra@gmail.com>
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
