[GRADLE-3259] Incremental Java compiler does not work with annotation processors Created: 10/Mar/15  Updated: 03/Feb/17  Resolved: 03/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Duplicate Votes: 19


See linked forum issue.

Comment by Gradle Forums [ 10/Mar/15 ]

Hi Luzi,

This will require changes to the incremental compiler implementation. There's no flag or anything like that to turn on and make it work unfortunately.

Comment by Rakesh Panati [ 24/Jan/16 ]


The forum question link seems to have expired. However, I would like to know if this bug is being planned for a fix.

Comment by Volo Idolon [ 10/Jun/16 ]

Adam Murdoch Is there any plans for this issue?
Currently it prevents incremental compilation on most of Android projects (as nearly any project these days use one of Dagger / ButterKnife / EventBus / AutoParcelable etc): https://code.google.com/p/android/issues/detail?id=200043

Comment by Alexander [ 25/Aug/16 ]

This should be fairly trivial to implement. Annotation processors are already expected to report dependencies between existing and generated code files via compiler API: https://docs.oracle.com/javase/7/docs/api/javax/annotation/processing/Filer.html. Gradle just have to get those dependencies from compiler and account for them during incremental compilation process. If the annotation processor fails to report dependencies, just treat that as compilation error.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Christian Kapplmüller [ 15/Nov/16 ]

Everything is complete, and we still advocate for this issue.

Comment by STEPHANE NICOLAS [ 29/Jan/17 ]

This is probably the most fundamental issue in Android builds that impacts developers productivity in our team, and actually probably the main motivation for us to soon consider moving to another build system. That's quite a pity !

FYI : https://code.google.com/p/android/issues/detail?id=200043

Comment by Eric Wendelin [ 03/Feb/17 ]

This has been migrated to https://github.com/gradle/gradle/issues/1320

All I can say right now is that we hear your collective voices loud and clear on this.

Generated at Wed Jun 30 12:44:09 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.