Provide java_common.merge interface for Java compilation of proto libraries Remove `exports`, `runtime_deps` parameters and introduce `merge_java_outputs`, `merge_source_jars` parameters. Drop corresponding providers. This optimisation corresponds to optimisations done natively. The new parameters are only available in builtins. Natively only `JavaCompilationArgsProvider`, `JavaCcInfoProvider` are merged from the deps. `java_common.merge` with `include_compilation_info` disabled provides `JavaCompilationArgsProvider`, `JavaCcInfoProvider` and additionally `JavaPluginInfo`, `runtimeJars` and `constraints`. Additional providers are empty in case of Java proto libraries. (Exception are `constraints`, which are used in `java_lite_proto_library`). In both cases `JavaRuleOutputJarsProvider`, `JavaSourceJarsProvider`, `JavaGenJarsProvider`, `JavaCompilationInfoProvider` are dropped (for optimisation). PiperOrigin-RevId: 451966776 Change-Id: I7459f9f62b7a4e6d14c26a502544b1318e6bdad7
{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
