Closed wbervoets closed 2 years ago
autonomousapps
commented
2 years ago Thanks for the report.
Something happened that violated an invariant in the plugin. I'll take a look and might have questions for you to help reproduce this. You can try an earlier version in the meanwhile, ideally rc01, possibly with -Ddependency.analysis.old.model=true.
cosic
commented
2 years ago I've got the same issue
* What went wrong:
Execution failed for task ':dev-ui:computeAdvice'.
> A failure occurred while executing com.autonomousapps.tasks.ComputeAdviceTask$ComputeAdviceAction
> Annotation processor usages can only be changed, not added.Enviroment:
I tried to execute
./gradlew buildHealth -Ddependency.analysis.old.model=truefor 1.0.0-rc02 version – got the same issue
for 1.0.0-rc01 and 0.80.0 versions – got Unused dependencies which should be removed: implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.6.10") issue from #444
wbervoets
commented
2 years ago fyi RC01 with -Ddependency.analysis.old.model=true does complete succesfully. Please let me know how I can be of further help debugging the issue
autonomousapps
commented
2 years ago If possible, it would be extremely useful to share a zip of your ${module}/build/reports/dependency-analysis directory for the module where this error appears. Those are all human-readable files, mainly json, and I can use that to diagnose the problem and then write regression tests once I have a solution.
Additionally or alternatively, minimal reproducers are always welcome.
autonomousapps
commented
2 years ago @wbervoets do you use the dagger.hilt.android.plugin plugin? Do you happen to know if declaring kapt 'com.google.dagger:hilt-compiler' also has the effect of adding kapt 'com.google.dagger:dagger-compiler'?
One thing you can try is to update your build.gradle to add kapt 'com.google.dagger:dagger-compiler' as an explicit dependency. Then run buildHealth again with rc02. If it succeeds, then that confirms my hypothesis that the plugin is tripping over the fact that it finds dagger-compiler on the kapt classpath but doesn't see it being declared.
If you have time, it might also be interesting if you could put together a small sample project using Hilt so I can investigate such a setup in more detail. Thanks!
wbervoets
commented
2 years ago @autonomousapps I can confirm that by adding kapt 'com.google.dagger:dagger-compiler' or (annotationProcessor for java modules) to all the affected modules fixes buildHealth with rc02
I'm using Dagger Hilt in my project (which provides a standard way to incorporate Dagger dependency injection into an Android application)? You can find more information about here https://dagger.dev/hilt/gradle-setup I am using the dagger.hilt.android.plugin for the reasons mentioned in the above URL.
I'm right now still recovering from illness, I'll try to create a small sample project next week.
autonomousapps
commented
2 years ago I have a fix for the crash in the PR I just linked. However, it will lead to advice that Hilt users would probably find confusing. When you provide a minimal reproducer, I'll move forward with the next step.
I'm getting the below exception: Exception Annotation processor usages can only be changed, not added
Any idea why this would be triggered? Parallel gradle build?
Plugin version 1.0.0 RC2
Gradle version Gradle 7.3.3
(Optional) Android Gradle Plugin (AGP) version AGP 7.1.1
Describe the bug Exception during buildHealth execution
To Reproduce Steps to reproduce the behavior:
gradlew buildHealth on root module