| commit | 276fb093b83c37d9c4d2b6df01c04700e7aa3346 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri Mar 25 12:37:42 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 25 12:39:05 2022 -0700 |
| tree | e045417cb8ba629408311d830338883002ef504f | |
| parent | 036564590d91ba445d3683abae8a7885c1d32d52 [diff] |
Packaging support for deploy JAR embedded JDK files (hermetic Java). This is the initial implementation that supports packaging runtime needed JDK files into deploy JAR, which is part of the phase III development for hermetic Java support (b/212719968). - The runtime needed JDK files specified via --resources flag are packaged as regular JAR entries in deploy JAR. Any JDK file that needs to be packaged at page aligned offset should not be included in --resource input list. - JDK 'lib/modules' file has page alignment requirement (runtime mmap the modules image). A new singlejar flag is introduced for specifying the lib/modules file: * --jdk_lib_modules <jdk_lib_modules_path> Following manifest attribute is written in the JAR META-INF/MANIFEST.MF, if lib/modules is specified via the new flag: * JDK-Lib-Modules-Offset: <offset> The lib/modules offset information will be used at runtime in JDK when mapping the file. Please see more details on design requirements/considerations and decisions in[] The support for launcher part is handled by unknown commit. RELNOTES: Packaging support for deploy JAR embedded JDK files (hermetic Java). PiperOrigin-RevId: 437310998
{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
