Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix IntellijAspectTest to recognize both "//foo:bar" and "@//foo:bar" labels #3779

Closed
wants to merge 1 commit into from

Conversation

copybara-service[bot]
Copy link

Fix IntellijAspectTest to recognize both "//foo:bar" and "@//foo:bar" labels

Both mean the same thing in a monorepo, but only the latter is unambiguous, since the former could mean different things from different repos. Bazel will generate the latter for absolute labels in the main repo in a future release, and this change is forwards-compatible with that.

See bazelbuild/bazel#15916 for more information.

… labels

Both mean the same thing in a monorepo, but only the latter is unambiguous, since the former could mean different things from different repos. Bazel will generate the latter for absolute labels in the main repo in a future release, and this change is forwards-compatible with that.

See bazelbuild/bazel#15916 for more information.

PiperOrigin-RevId: 462117644
@copybara-service copybara-service bot closed this Sep 9, 2022
@copybara-service copybara-service bot deleted the test_462117644 branch September 9, 2022 14:53
@ThomasCJY
Copy link

@mai93 @vsiva Can we reopen this PR? We hit a similar issue in bazel Android Studio plugin recently and this commit seems to be the fix.

@mai93
Copy link
Collaborator

mai93 commented Feb 21, 2023

IIUC this change was still incorrect for some cases that is why the PR was closed and a different workaround was implemented in 41d1964. Can you please open an issue for the problem you are seeing with Android Studio plugin recently?

@ThomasCJY
Copy link

ThomasCJY commented Feb 23, 2023

nvm we tried the latest plugin and it seems like it's fixed already

@ThomasCJY
Copy link

@mai93 turns out this still happens on instrumentation test targets. I made a patch fix for it, ptal #4529

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants