Saturday, February 23, 2019

Re: Annotation processing in Eclipse

On Friday, February 22, 2019 at 8:40:27 PM UTC+1, Lars wrote:
Dagger does not play well with the incremental compiler of eclipse - see
Background is, that the standard annotation processor does only know things from the current runs and this is limited (by design) for an incremental compiler. Whitout some additional (non-standard) components to see the full code or to give the compiler more hints for the dependencies for the generated classes, this works only with a full compile.

Dagger works great with Gradle incremental compilation and annotation processing, so it's not a problem of incremental compilation/processing per se, but likely the bugs that litter the Eclipse compiler (see Jens' answer).

Eclipse annotation processing is known to be broken in many ways, though things are getting better with each release, so first make sure you use the very latest version of Eclipse.
You may want to disable "in the editor" processing and explicitly run annotation processing by rebuilding the project (or something like that; I haven't used Eclipse for years, and I don't let my IDE do anything build-related so 🤷)

You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment