| commit | 76fac817e4dbe5aaece9ed6a962e1cc94815d4d6 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Thu Apr 14 11:40:13 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 14 11:41:22 2022 -0700 |
| tree | 2bfeca921a8d3cba6b7feebb0c72499f9ce69c88 | |
| parent | ad7dae3ad3b31f44eb9a5e743daefccca1f544a3 [diff] |
Add Blaze support for "local" optimization of individual Java libraries. This should allow optimization on a per-library level within Blaze of every artifact generated by javac. The purpose of this is for improved test coverage by the AppReduce team and is not intended for general use. See this thread for more context: [] This change should only add a dependency on the bytecode optimizer when --experimental_local_java_optimizations is true, so it should be a no-op for all standard builds. I implemented this in Java instead of Starlark because it allowed me to modify the produced JavaInfo much more simply. If this was implemented in Starlark, I'd have to be able to replace the JavaInfo object produced by a java_* target since the JavaInfo from javac is currently all still wired up in Java. My attempts at structuring the change that way seemed much more invasive to JavaInfo and more brittle. PiperOrigin-RevId: 441814811
{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
