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 <m...@talios.com> 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 >
