| commit | 8174262bf946e31df86476014c6f231f46ca0882 | [log] [tgz] |
|---|---|---|
| author | gregce <gregce@google.com> | Fri Jan 28 13:00:59 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jan 28 13:02:46 2022 -0800 |
| tree | cfc236382ea6805d16d0939b626739ee119fe6d8 | |
| parent | 791f13b89991b8046a28b9a660682745e8aa6620 [diff] |
Simplify `DependencyResolver` attribute resolution. - Move the logic for resolving aspect/rule merged attributes into `AspectAwareAttributeMapper` (this is a dedicated class for this purpose) - Make `AspectAwareAttributeMapper` more powerful (it now resolves *values*) with less code - Simplify `DependencyResolver`'s code path - Eliminate the duplicate logic for excluding "nodep" dependencies - Reduce LoC by a nice little amount Testing: since this is core logic, all changes have test coverage - if not directly then by the build logic that expects the invariants preserved here PiperOrigin-RevId: 424938613
{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
