lint standalone plugin doesn't handle gradleApi() dependency properly [198453608]

Fixed

Bug

adexe s nau

Status Update

No update yet.

Description

sp...@google.com

created issue #1

Sep 1, 2021 06:27PM

Appears to be caused by Change-Id: I563359b0ae4acb6ffc47e2791e173f3d78ca3fd3

* What went wrong:
Execution failed for task ':buildSrc-tests:lintAnalyze'.
> Don't know how to handle ComponentIdentifier 'Gradle API'of type class org.gradle.internal.component.local.model.OpaqueComponentIdentifier

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':buildSrc-tests:lintAnalyze'.
Caused by: java.lang.RuntimeException: Don't know how to handle ComponentIdentifier 'Gradle API'of type class org.gradle.internal.component.local.model.OpaqueComponentIdentifier
	at com.android.build.gradle.internal.ide.dependencies.ResolvedArtifact.computeModelAddress(ResolvedArtifact.kt:167)
	at com.android.build.gradle.internal.lint.LintDependencyModelBuilder.addArtifact(LintDependenciesModelBuilder.kt:70)
	at com.android.build.gradle.internal.ide.dependencies.ArtifactDependencyGraph.createDependencies(ArtifactDependencyGraph.java:91)
	at com.android.build.gradle.internal.lint.ArtifactInput.computeDependencies$gradle_core(AndroidLintInputs.kt:1590)
	at com.android.build.gradle.internal.lint.AndroidArtifactInput.toLintModel$gradle_core(AndroidLintInputs.kt:1298)
	at com.android.build.gradle.internal.lint.VariantInputs.toLintModel(AndroidLintInputs.kt:922)
	at com.android.build.gradle.internal.lint.AndroidLintAnalysisTask.writeLintModelFile(AndroidLintAnalysisTask.kt:136)
	at com.android.build.gradle.internal.lint.AndroidLintAnalysisTask.doTaskAction(AndroidLintAnalysisTask.kt:122)
	at com.android.build.gradle.internal.tasks.NonIncrementalTask$taskAction$$inlined$recordTaskAction$1.invoke(BaseTask.kt:66)
	at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:51)
	at com.android.build.gradle.internal.tasks.NonIncrementalTask.taskAction(NonIncrementalTask.kt:98)

Comments

al...@google.com <al...@google.com> #2Sep 2, 2021 04:29PM

Was there a temporary fix that you applied here to get the output in b/198533108? I'd like to clear that bug out, but I'm hitting this one first.

al...@google.com <al...@google.com> #3Sep 2, 2021 04:31PM

Strike that, I was looking at the wrong ABTD run. This one includes your fix.

sp...@google.com <sp...@google.com> #4Sep 7, 2021 06:42PM

Moving to P2 and renaming now that the workaround has been merged.

dr...@gmail.com <dr...@gmail.com> #5Nov 1, 2021 08:39PM

Is a real fix for this going to happen? It seems like the fix that was applied here was to stop crashing but silently ignore the dependency instead of adding it. I'm trying to write lint checks for Gradle plugins, which is not really possible when the gradleApi() artifact is unavailable to Lint.

tn...@google.com <tn...@google.com> #6Nov 1, 2021 08:47PM

Adding Chris for comment until Scott is back.

dr...@gmail.com <dr...@gmail.com> #7May 3, 2022 05:55PM

Any update on this? Just tried with AGP 7.3.0-alpha09 and it seems like there's no change to the behavior.

sp...@google.com <sp...@google.com> #8May 3, 2022 05:59PM

Sorry, no update on this. It's still on our radar, but other work has taken priority. Increasing from P2 -> P1.

dr...@gmail.com <dr...@gmail.com> #9Jan 13, 2023 11:37PM

Would still love to see this fixed so we can unlock lint for use in Gradle plugins! Just tried on AGP 8.0.0-alpha11 and still seeing the same behavior.

sp...@google.com <sp...@google.com> #10Sep 15, 2023 02:23PM

Marked as fixed.

This is fixed here. The fix will be in AGP 8.3.0-alpha05.

an...@google.com <an...@google.com> #11Sep 21, 2023 09:04PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Iguana | 2023.2.1 Canary 5
Android Gradle Plugin 8.3.0-alpha05

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!