Re: Anyone using annotationProcessorPaths in maven-compiler-plugin

Am Sonntag, 27. März 2016 schrieb Mark Derricutt : > On 27 Mar 2016, at 0:28, Andreas Gudian wrote: > > > Right, in 3.5.1 I fixed an oversight that caused the modules direct > > dependencies to also show up in -processorpath. > > Hrm, actually that's the reason I was looking at using this method

Re: Anyone using annotationProcessorPaths in maven-compiler-plugin

On 27 Mar 2016, at 0:28, Andreas Gudian wrote: > Right, in 3.5.1 I fixed an oversight that caused the modules direct > dependencies to also show up in -processorpath. Hrm, actually that's the reason I was looking at using this method over just listing the deps in the first place - since the

Re: Anyone using annotationProcessorPaths in maven-compiler-plugin

Right, in 3.5.1 I fixed an oversight that caused the modules direct dependencies to also show up in -processorpath. So anyway, in 3.5.1, it should work just as expected. Are you maybe using a different plexus-compiler implementation by configuring an addidtional plugin-dependency? Here's another

Re: Anyone using annotationProcessorPaths in maven-compiler-plugin

This was using 1.8 and the 3.5.1 of the compiler plugin ( which seems to have quite major differences in behaviour to 3.5 ), which I think it uses the tools api and not calling javac ( I do note theres an option to force using javac tho ) so might give that a shot. -- "Great artists are

Re: Anyone using annotationProcessorPaths in maven-compiler-plugin

Have you set source and target to at least 1.6 or 6? You should see the -processorpath argument being passed to JavaC when running with -X. Le jeu. 24 mars 2016 00:37, Mark Derricutt a écrit : > Hey all, > > Has anyone successfully used the new setting > in the

Re: Anyone using annotationProcessorPaths in maven-compiler-plugin

Hi Mark, The javadoc of annotationProcessorPaths [1] is not very reassuring for your intended use case: "Classpath elements to supply as annotation processor path. If specified, the compiler will detect annotation processors only in those classpath elements." That makes it sounds like it merely

Re: Anyone using annotationProcessorPaths in maven-compiler-plugin

The only annotation processor I use is Google's auto-service. I didn't find this to be setting to be useful at all in that case, because I still need the auto-service on the classpath (as an optional dependency) so I can actually use the @AutoService annotation in my source. I didn't try it with

Anyone using annotationProcessorPaths in maven-compiler-plugin

Hey all, Has anyone successfully used the new `` setting in the `maven-compiler-plugin` at all? I'm adding: ```xml com.google.dagger dagger-compiler 2.1 ``` to my compiler plugins configuration but it doesn't seem to work, when running maven with -X I see the