| commit | 53ff268c7e7d61614e3fdba74d55103e64b8f80b | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Thu Feb 16 11:19:02 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 16 11:20:20 2023 -0800 |
| tree | cd0df2806a1d12ad994ea15f4fef849e50204ea9 | |
| parent | f39272a6e69bedf0b094048412eff3ba7186faae [diff] |
Support packaging the JDK default CDS image in hermetic deploy JAR using 'java_runtime.default_cds' attribute. If a hermetic 'java_runtime' target specifies the 'default_cds' attribute, and the 'java_binary' target does not provide its own CDS archive (by specifying the 'classlist' attribute), the java_runtime's default CDS is packaged when building a hermetic deploy JAR. This CL simply bridges the current hermetic support with the earlier work (unknown commit has added the related single JAR connection for embedding CDS) for deploy JAR embedded CDS. The 'java_runtime' change is in unknown commit, which has additional integration test cases for the hermetic default CDS. #hermetic-java-static-linking PiperOrigin-RevId: 510195888 Change-Id: I51e8fef364bcb7c53c42d010cd51dbc4f689247c
{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
