Skip to content

[AOSP-pick] Never ask for artifacts without output group #7366

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

Merged
merged 1 commit into from
Feb 26, 2025

Conversation

sellophane
Copy link
Collaborator

Cherry pick AOSP commit b228d1ef2bdb093b73203176ec8158061042505e.

  1. Builds may get multiple aspects applied resulting in multiple
    additional artifacts returned.

  2. Make getOutputGroupTargetArtifacts return all artifacts declared by
    the target as its outputs instead of ambiguously defined direct
    artifacts, which in its current implementation is implementation
    dependent and returns top level named file sets only. Note, a single
    target may itself produce multiple nested file sets without
    participation of other targets at all. File sets basically follow the
    structure fo depsets. Perhaps the amount of logging in callers
    reflects the incorrect behavior.

  3. When requesting AndroidDeployInfo from local build mirror the
    implementation providing support for remote builds and pass the
    output group name explicitly. note, these two implementations need
    to converged before they can be merged.

Bug: 385469770
Bug: 327638725
Test: existing
Change-Id: Idfb90474e74cd6e4fa9978452f687138c69df13c

AOSP: b228d1ef2bdb093b73203176ec8158061042505e

1. Builds may get multiple aspects applied resulting in multiple
   additional artifacts returned.

2. Make `getOutputGroupTargetArtifacts` return all artifacts declared by
   the target as its outputs instead of ambiguously defined direct
   artifacts, which in its current implementation is implementation
   dependent and returns top level named file sets only. Note, a single
   target may itself produce multiple nested file sets without
   participation of other targets at all. File sets basically follow the
   structure fo depsets. Perhaps the amount of logging in callers
   reflects the incorrect behavior.

3. When requesting `AndroidDeployInfo` from local build mirror the
   implementation providing support for remote builds and pass the
   output group name explicitly. note, these two implementations need
   to converged before they can be merged.

Bug: 385469770
Bug: 327638725
Test: existing
Change-Id: Idfb90474e74cd6e4fa9978452f687138c69df13c

AOSP: b228d1ef2bdb093b73203176ec8158061042505e
@LeFrosch LeFrosch merged commit 5ebb635 into master Feb 26, 2025
9 checks passed
@github-project-automation github-project-automation bot moved this from Untriaged to Done in Bazel IntelliJ Plugin Feb 26, 2025
@github-actions github-actions bot removed the awaiting-review Awaiting review from Bazel team on PRs label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product: CLion CLion plugin product: GoLand GoLand plugin product: IntelliJ IntelliJ plugin
Projects
Development

Successfully merging this pull request may close these issues.

4 participants