| commit | 48953d757bb99f1b243df7f02ef09b19b12fdd59 | [log] [tgz] |
|---|---|---|
| author | wyv <wyv@google.com> | Tue May 03 04:36:18 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue May 03 04:37:37 2022 -0700 |
| tree | 66448ba443ca17bdae5da1b16e575594122712f1 | |
| parent | ae349e9368f90bc5cf27f51ecc773ada9e3a514c [diff] |
Remove most usages of PackageIdentifier#parse(String)
This parse method doesn't use repo mapping and can thus be potentially problematic. We should replace it with one that does respect repo mapping; that CL will follow this one.
The usages replaced in this CL are mostly :
1. Test usages, with something to the effect of `PackageIdentifier.parse("@//foo")`. These can simply be replaced with `PackageIdentifier.createInMainRepo("foo")`.
2. Certain prod usages where we construct a package identifier string from a RepositoryName object and a path segment. This can be done directly with `PackageIdentifier.create(repo, pkg)`, instead of `PackageIdentifier.parse(repo.toString() + "//" + pkg)`.
- Most notably, this includes some changes in the TargetPattern / query logic that were using a similar idiom for labels (constructing a string and re-parsing it, instead of simply constructing from parts).
PiperOrigin-RevId: 446162604
{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
