| commit | 0511bb4b73a4b566636ffdcc930cbb682313de97 | [log] [tgz] |
|---|---|---|
| author | Googler <brandjon@google.com> | Wed May 17 14:34:51 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 17 14:36:09 2023 -0700 |
| tree | 1857c07dbad3829148931d0f05aa3214b95607cf | |
| parent | 517d4f139e63330a19043df3474958a8ed2cbf6d [diff] |
Eliminate PackageArgument The package() function is now implemented by a @StarlarkMethod rather than an anonymous subclass of StarlarkCallable. The PackageArgument machinery is deleted. The convert-and-process approach is instead inlined into a series of if-elses for each argument (with the convert step using a helper to reduce repetition). The big if-else is factored out into an overridable method, so other implementations of package() can add their own parameters on top. The package() symbol is now registered on the ConfiguredRuleClassProvider like any other BUILD toplevel. Removed its special casing in BazelStarlarkEnvironment, and the ability to register PackageArguments with the CRCP. Fixed a copy-paste error where the "default_applicable_licenses" param would claim to be "default_package_metadata" for the purposes of error messages. PiperOrigin-RevId: 532911239 Change-Id: I957354e0a4e32f7922b510c5537f56c6aff72ab9
{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
