diff options
| author | 2023-04-12 19:05:49 +0000 | |
|---|---|---|
| committer | 2023-04-27 01:43:00 +0000 | |
| commit | f57a966b6694da970e99f519919f9b845b713163 (patch) | |
| tree | 7052e5deb95adc54d5286f2e40f6d0f3b96bfdd7 /java/java.go | |
| parent | c741160d81b5f192a33ef476cbfd4b8f712a05c6 (diff) | |
Ignore test apexes from bp2build generated tags
The core problem I am trying to solve is making sure that stub
libraries in Bazel have a single apex available. In Soong, this will be
enforced using some graph walk which is not easy to port to Bazel.
However, we might need to revisit this when we build the enforcement
mechanism in Bazel. We likely need a `test_for` on the top level
apex_test Bazel rule so that the test apex is _allowed_ to link against impl
of the library it is trying to test.
(This CL retricts this to cc_library, I can expand this to other modules
if this is the right approach.)
Bug: 277651159
Change-Id: Iaeec22c5626df79a33785c766ed29102b1da403e
Diffstat (limited to 'java/java.go')
0 files changed, 0 insertions, 0 deletions