| commit | dbb6e9954b6e4423f727feb2719ffc75a93b514b | [log] [tgz] |
|---|---|---|
| author | Zhongpeng Lin <zplin@uber.com> | Thu Mar 31 10:38:15 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 31 10:39:40 2022 -0700 |
| tree | e51355fc6f2c83d937c7e71c05f48ced80be8c63 | |
| parent | 299022ca2dc49b6cb27b2674f933755306ae8b9b [diff] |
Fixing dependencies of //external package
We need to query `kind('source file', deps(//external:*))` for sparse checkout, but were block by two issues:
* `//external:remotejdk11_linux` depends on `tools/jdk/jdk.BUILD`, but it was not exported. Although this is not a problem for build, queries like `kind('source file', deps(//external:remotejdk11_linux))` would fail.
* `//external:android_sdk_for_testing` is an alias for `//:dummy`, which is not available in other repositories. This also caused #8175.
This pull request fixed both, including #8175.
Closes #15134.
PiperOrigin-RevId: 438605051
{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
