| commit | 9004fc7e36591bf8277eb85232cbeedaf18995b7 | [log] [tgz] |
|---|---|---|
| author | Noa Resare <noa@resare.com> | Fri Apr 08 04:31:39 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Apr 08 04:32:59 2022 -0700 |
| tree | cb8a47c4c673e4ab30f8e9be9def3448bee31bb2 | |
| parent | 7d3fb993f55b35081786c3fe00cf3bebb89574f3 [diff] |
Have README.md in java_tools release reference the right target I was trying to figure out what produced the files included in https://github.com/bazelbuild/java_tools/releases/download/java_v11.6/java_tools-v11.6.zip that happens to have some instructions on how to re-produce the contents of the file. However, it turns out that the instructions in README.md references the wrong build target, which made it a bit confusing. This change updates the target to one that produces a zip that seem to contain the right files. Closes #15093. PiperOrigin-RevId: 440331100
{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
