Re: Using "annotationProcessorPaths" together with version ranges

2017-08-23 Thread Mark Derricutt 
On 24 Aug 2017, at 9:49, Andreas Gudian wrote:

> Yupp, I'm afraid neither version ranges nor information from any
> dependencyManagement sections are considered.
>
> Only the plain versions or properties work, and transitive dependencies are
> pulled in

Yeh, we use properties as a workaround here - we actually resolve our ranges 
external to Maven - in a `pom.deps` files, which in part is used to bootstrap 
version properties ( the actual `pom.xml` files get there `` elements 
of plugins/dependencies rewritten to hard locked `[xxx]` versions as well.

Also since we shared compiler plugin settings across projects, it means I have 
to list all possible combinations of annotationProcessors we know we support ( 
which is not many, but would be nice to control per project ).

Mark


---
"The ease with which a change can be implemented has no relevance at all to 
whether it is the right change for the (Java) Platform for all time."  
Mark Reinhold.

Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt


signature.asc
Description: OpenPGP digital signature

Re: Using "annotationProcessorPaths" together with version ranges

2017-08-23 Thread Andreas Gudian 
Yupp, I'm afraid neither version ranges nor information from any
dependencyManagement sections are considered.

Only the plain versions or properties work, and transitive dependencies are
pulled in.

And I agree that a special scope would have been a nice alternative
solution, but that would have opened up a whole can of worms in all kinds
of places...



Mark Derricutt  schrieb am Fr. 18. Aug. 2017 um 06:53:

> On 17 Aug 2017, at 19:33, Cristian Spiescu wrote:
>
> When using maven-compiler-plugin with "annotationProcessorPaths", and I
> specify a dependency with a version range: it doesn't seem to work. I have
> done some debugging, and I see that the general dependency solving
> mechanism (that does
>
> I really wish we could have a new 'annotation' scope and NOT use
> 'annotationProcessorPaths', it makes things really ik to work with when
> using parents/tiles and common compiler plugin settings.
>
> Interestingly, the DTD doesn't actually specify a strict set of scopes,
> and neither does the documentation it seems.
>
> Mark
> --
>
> "The ease with which a change can be implemented has no relevance at all
> to whether it is the right change for the (Java) Platform for all time." —
> Mark Reinhold.
>
> Mark Derricutt
> http://www.theoryinpractice.net
> http://www.chaliceofblood.net
> http://plus.google.com/+MarkDerricutt
> http://twitter.com/talios
> http://facebook.com/mderricutt
>

Re: Using "annotationProcessorPaths" together with version ranges

2017-08-17 Thread Mark Derricutt 
On 17 Aug 2017, at 19:33, Cristian Spiescu wrote:

> When using maven-compiler-plugin with "annotationProcessorPaths", and I 
> specify a dependency with a version range: it doesn't seem to work. I have 
> done some debugging, and I see that the general dependency solving mechanism 
> (that does

I really wish we could have a new 'annotation' scope and NOT use 
'annotationProcessorPaths', it makes things really ik to work with when using 
parents/tiles and common compiler plugin settings.

Interestingly, the DTD doesn't actually specify a strict set of scopes, and 
neither does the documentation it seems.

Mark

---
"The ease with which a change can be implemented has no relevance at all to 
whether it is the right change for the (Java) Platform for all time."  
Mark Reinhold.

Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt


signature.asc
Description: OpenPGP digital signature

Using "annotationProcessorPaths" together with version ranges

2017-08-17 Thread Cristian Spiescu 

Hello,

I think I have spotted a bug, but I'm not 100% sure.

When using maven-compiler-plugin with "annotationProcessorPaths", and I 
specify a dependency with a version range: it doesn't seem to work. I 
have done some debugging, and I see that the general dependency solving 
mechanism (that does support version ranges) doesn't seem to be used 
when trying to resolve the dependencies from "annotationProcessorPaths". 
So if I specify [1.0.0, ), then maven actually tryies 
to use the version as-is, actually creating a directory "[1.0.0,)" in 
the local maven repo.


Does anyone has any pointers on this?

Thanks a lot in advance!

Cristian.


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org