| commit | aa47fd1de7da398adb6e71b6122ced23c067a30b | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Fri Oct 18 10:37:04 2024 +0200 |
| committer | GitHub <noreply@github.com> | Fri Oct 18 08:37:04 2024 +0000 |
| tree | d6b86b5d13183ca8ada9f223882a2773b0c21d7d | |
| parent | a99de87f5b7ac4f8c9f4ffd2ebc2481567db7512 [diff] |
[7.4.0] Blaze/Bazel changes for Java 17 Record desugaring (#24030) createDexMergerActions continues to be exposed to Starlark due to it's use for SpawnActionTemplate which is not exposed to Starlark. We must pass a file containing global information to the final dexmerging step in order to support Java 17 Record desugaring. This change adds an optional parameter to the Starlark interface to forward the globals file to the Dex Merger. PiperOrigin-RevId: 660045021 Change-Id: Ie3b961ff2687f48ca29a94e67180c0e5875ddbe3 Commit https://github.com/bazelbuild/bazel/commit/2daa0a3d893a3c18021e7c1191d4cacc270dd062 Co-authored-by: Andrew Sinclair <asinclair@google.com>
{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
