On Wed, Aug 21, 2013 at 3:19 AM, Baptiste Mathus <m...@batmat.net> wrote: > Wondering: is this strategy still gonna choose the newest version specified > even if I specify a version inside my pom? Or is it only gonna be used > between dependencies?
The behavior we actually need and want most of the time is for it to pick the newest version, *even if there is a direct dependency from your pom*. > If the latter, I may agree it can be of interest. > But with the first I guess it would get crazy not being able to force the > version to be used. Yeah, I know what you mean, and I thought about this too. It is true that every once in a while, you may really need to force it to use an older version (even though some dependency is using a newer version). That should be pretty rare, but it definitely could happen. My idea to solve this was to add support for a <forcever>true</forcever> in the <dependency> declaration. Thoughts? Phillip --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
