commit | 9331df2976a8a16a2cfa5c4a98ae19ac0f8008fe | [log] [tgz] |
---|---|---|
author | ilist <ilist@google.com> | Wed Jan 26 07:59:37 2022 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 26 08:01:06 2022 -0800 |
tree | 3022f60aa0e93a74f7b0994d4775692e284cb388 | |
parent | 768751c076c6d556aeba38151ac82323a1001f75 [diff] |
Pass rule attributes to base/java common action via parameters. The change strives to make parts of Java rules more composable (Along the way potentially improving also documentation and testability). I factored out `_collect_deps`, `_collect_plugins` and `collect_resources` calls. The last one needs to be pulled one level higher because a mix of Files and Attributes needed in the process of collection. (This is resolved in follow up changes). `construct_defaultinfo` was also pulled one level higher in call-tree. This presented an opportunity to slightly simplify semantics.postprocess_plugin. PiperOrigin-RevId: 424346722
{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