| commit | 9b39ccaa33069c9f5688bef477abcd75e4378f04 | [log] [tgz] |
|---|---|---|
| author | Ivo List <ilist@google.com> | Thu Mar 07 17:28:23 2024 +0100 |
| committer | GitHub <noreply@github.com> | Thu Mar 07 16:28:23 2024 +0000 |
| tree | fd38e01e66fb41b0e45c25fbbb67a836b6c41272 | |
| parent | 2b440b8e09d5b9ebe2f5f5292f19564b3f529679 [diff] |
[7.1.0] Expose AndroidIdeInfo in android_common (#21607) Previously https://github.com/bazelbuild/bazel/commit/916c3f5a649926f07a8390893539b560646a192e exposed the provider on top-level to support IntelliJ aspects. Exposing it over android_common, makes it possible to detect its presence in Starlark code via `getattr(android_common, "AndroidIdeInfo")`. With this detection it's easier to support older Bazel versions. Without exposing it via android_common, detecting AndroidIdeInfo presence in Bazel world is only possible using a new dependency on @bazel_features in IntelliJ aspects. Fixes: https://github.com/bazelbuild/bazel/issues/21544 PiperOrigin-RevId: 613580552 Change-Id: I214024facbdc9ac7742bf98575101bd624d4a6a7
{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
