| commit | 3649324afde591bb67b5e0ebfad65e8ea56d0580 | [log] [tgz] |
|---|---|---|
| author | Googler <ilist@google.com> | Mon May 30 23:07:42 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon May 30 23:08:56 2022 -0700 |
| tree | 49f7146d46bcc63aa4c582a83bf8ee822eaab47a | |
| parent | 4c26c3a1768f69ccff8517862bd5b09a958b3564 [diff] |
Provide java_common.compile interface for Java compilation of proto libraries Remove `create_output_source_jar` parameter and infer its value. The value is `false` when precisely 1 source jar is on the input which is also the `output_source_jar`. Introduce `include_compilation_info` parameter. It may be disabled only in builtins. When disabled the function drops `JavaCompilationInfo` and `JavaGenJarsProvider`.This corresponds to optimisations done natively. Native Java proto compilation code provides `JavaRuleOutputJarsProvider`, truncated `JavaSourceJarsProvider`, `JavaCcInfoProvider`. Benchmarks show that truncating `JavaSourceJarsProvider` is unnecessary. PiperOrigin-RevId: 451967306 Change-Id: I033e690ffb1df36e00203f5447675861bfdfdb52
{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
