commit | 5843aad1be87c8117e85ade9e9c9c0c05b635f21 | [log] [tgz] |
---|---|---|
author | Xùdōng Yáng <wyverald@gmail.com> | Tue Nov 07 14:15:49 2023 -0800 |
committer | GitHub <noreply@github.com> | Tue Nov 07 22:15:49 2023 +0000 |
tree | b77f56c91346aca4291da20ec2ab6edba046161c | |
parent | cf8f94df589aa40b9389ab83da0869ab83d508d7 [diff] |
[7.0.0] Fix JVM repository rules with Bzlmod (#20088) * Lets the `http_jar` and `jvm_{maven_}import_external` rules load from `@rules_java` as resolved within `@bazel_tools` rather than the calling module extension's repository. * Uses the user-provided apparent repository name in `jvm_maven_import_external` to generate a target name for the jar that makes the shorthand `@my_import` form work with Bzlmod. * Ensure that Bazel loads the `http_jar` rule with the full repo mapping for `bazel_tools` so that it sees `rules_java`, while still loading `http_archive` with a trivial repo mapping to prevent a cycle during module repo creation. This requires introducing a new key type for `BzlLoadFunction`. Closes #19997. PiperOrigin-RevId: 579002601 Change-Id: I94c85e9759d0913384b10b9bbd0d0cb960cdd89a Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
{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