On Saturday, February 23, 2019 at 7:03:49 AM UTC-5, Thomas Broyer wrote:
> Eclipse annotation processing is known to be broken in many ways...
>
Yep. I took a look at the logs as Jens suggested and found an exception
from the dagger compiler. Eclipse is definitely not doing it
or 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 annota
Dagger does not play well with the incremental compiler of eclipse - see
https://stackoverflow.com/questions/41178320/does-dagger2-annotation-processor-supports-the-eclipse-incremental-compiler
Background is, that the standard annotation processor does only know things
from the current runs and
Have you checked the Eclipse error log window? I know we once examined
Dagger2 + AutoFactory and there was some bug in Eclipse JDT that caused
internal Eclipse exceptions to escape and thrown during annotation
processor execution which in turn stopped generating source files. Maybe
that issue
It's a slightly off-topic question but possibly an issue familiar to GWT
developers.
I'm using Dagger2 and AutoFactory and am quite happy with both. Eclipse,
however, does not play nicely with them. After saving any change, I will
usually end up with a broken build because Dagger doesn't
