Remove stamp attribute from deploy jar rule Since this rule may be invoked by users directly for java_test, we need to ensure we use the same `stamp` value for both the binary and the deploy jar. Unfortunately, the bazel implementation uses `java_common.get_build_info()` which looks up stamping on the rulecontext attribute. This means we need to perform this lookup during analysis of the java_binary/java_test. So we do that and pass the resolved build info files in java_binary/java_test to the deploy jar rule via the internal provider PiperOrigin-RevId: 510432399 Change-Id: I035858c7ee865cde851b4c67821d69bcbbb7d164
{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
