Re: IDEs, Dagger2 and annotationProcessorPaths

2016-12-17 Thread Raphael André Bauer
Absolutely right - it's not a Dagger2 issue at all. As dumb user of Dagger2 it's nevertheless unfortunate that the tooling aka IDE / Maven integration is not (yet) up to the job... I mean - Dagger2 was released 1.5 years ago... Best, Raphael On Sat, Dec 17, 2016 at 9:50 AM, Thomas Broyer wrote:

Re: IDEs, Dagger2 and annotationProcessorPaths

2016-12-17 Thread Thomas Broyer
Nothing to do with Dagger proper, it's a Maven and IDE integration issue. annotationProcessorPaths of maven-compiler-plugin is quite new (and with issues on its own) and it's not really surprising that IDEs haven't caught up yet. -- You received this message because you are subscribed to the Go

Re: IDEs, Dagger2 and annotationProcessorPaths

2016-12-16 Thread Raphael André Bauer
Thanks for all the hints. maven-processor-plugin seems to work with the IDEs, but I will have to do some more testing. A bit unfortunate that tooling for Dagger2 does not work out of the box... Cheers, Raphael On Thu, Dec 15, 2016 at 8:37 PM, Lars wrote: > Thanks for the answer! I tried to put

Re: IDEs, Dagger2 and annotationProcessorPaths

2016-12-15 Thread Lars
Thanks for the answer! I tried to put it to the Dagger Discuss group, but without luck/access to post. But may could give stackoverflow a try... -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emai

Re: IDEs, Dagger2 and annotationProcessorPaths

2016-12-15 Thread Thomas Broyer
This is a Dagger question and Dagger support is done on StackOverflow. But no I don't think you can use the incremental compiler (people have similar issues with Android/Gradle builds with the new incremental Jack toolchain) -- You received this message because you are subscribed to the Google

Re: IDEs, Dagger2 and annotationProcessorPaths

2016-12-15 Thread Lars
Does Dagger2 annotation processor supports the Eclipse incremental compiler? I setup Dagger2 with the sample app and after a full compile (after cleaning the project) everything works fine, but after small changes (module or component) and only an incremental compiler run nothing is updated (and

Re: IDEs, Dagger2 and annotationProcessorPaths

2016-12-14 Thread Ignacio Baca Moreno-Torres
I prefer to use maven-processor-plugin because I usually get better IDE integration. I use intellij, but from time to time I'll try it in eclipse and I think it work. https://github.com/ibaca/gwt-dagger2-coffee/blob/master/pom.xml On Thu, Dec 15, 2016 at 2:49 AM Juan Pablo Gardella < gardellajuanp

Re: IDEs, Dagger2 and annotationProcessorPaths

2016-12-14 Thread Juan Pablo Gardella
Check http://stackoverflow.com/a/35744298/741689 On Wed, 14 Dec 2016 at 20:03 Raphael André Bauer < raphael.andre.ba...@gmail.com> wrote: > Hi, > > > I am just playing around with GWT 2.8 and Dagger 2.8. I added Dagger 2 > via the compiler plugin and the Dagger compiler to > annotationProcessorP

IDEs, Dagger2 and annotationProcessorPaths

2016-12-14 Thread Raphael André Bauer
Hi, I am just playing around with GWT 2.8 and Dagger 2.8. I added Dagger 2 via the compiler plugin and the Dagger compiler to annotationProcessorPaths. When running mvn compile on the command line everything is fine. The generated DaggerMyAppComponent is generated properly and can be used in the