Separate main aspect prerequisites from rule and base aspects prerequisites
add `separate_aspect_deps` flag to guard this fix, when the flag is enabled the dependencies of the main aspect will be separated from those of the target and the base aspects. `ctx.attr.{attr_name}` will always get the attribute value from the main aspect and `ctx.rule.attr.{attr_name}` will get the value from the rule if it has an attribute with that name or from the base aspects attributes (first one in the aspects path wins).
PiperOrigin-RevId: 580292823
Change-Id: I719f8775c0c2aa582aed600387cb6b321cf5b639
{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
