Dagger compiler not incremental after upgrading to 2.23
See original GitHub issueAfter upgrading to Dagger 2.23 we noticed that Gradle started reporting the Dagger compiler as a non-incremental annotation processor:
Gradle may disable incremental compilation as the following annotation processors are not incremental: dagger-compiler-2.23.jar (com.google.dagger:dagger-compiler:2.23), dagger-android-processor-2.23.jar (com.google.dagger:dagger-android-processor:2.23).
Consider setting the experimental feature flag android.enableSeparateAnnotationProcessing=true in the gradle.properties file to run annotation processing in a separate task and make compilation incremental.
Not sure if it’s a problem but comparing the 2.23 jar with the 2.22.1 one we noticed that the Gradle configuration file is not in the top level META-INF
folder:
➜ ~ find **/incremental*
dagger-compiler-2.22.1/META-INF/gradle/incremental.annotation.processors
dagger-compiler-2.23/java/dagger/internal/codegen/META-INF/gradle/incremental.annotation.processors
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:6
Top Results From Across the Web
How to get rid of Incremental annotation processing requested ...
But the truth is that if any of the annotation processors are not incremental then none of them will be processed incrementally. This...
Read more >Compilation fails with "IllegalArgumentException: not a valid ...
Btw I just gave it a try with dagger 2.23.2 and I still get the following error with studio 3.6 canary 3 with...
Read more >Speeding Up Builds with Dagger Reflect
Then Dagger came along and alleviated this problem by generating code at compile time instead of using reflection at runtime.
Read more >pyQuil Documentation
QVM or compiler. After installing the SDK and updating pyQuil in Installation and Getting Started, see the migration guide to get caught.
Read more >Reverse Engineering Object-Oriented Systems into Umple
and programming since the end-product of umplification is not a separate model, but is an incremental change to the code/model.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve got a fix out internally, I hope to have this resolved and push a new version shortly
2.23.1 should be available on Maven Central now.