Hello,
I have two modules, say A and B, which are using the same library, one
is using 1.0.8 and one 1.0.14:
<dependency>
<groupId>net.anotheria</groupId>
<artifactId>ano-util</artifactId>
<version>1.0.14</version>
</dependency>
A third module (a web-app) uses both A and B. After I built the third
module, it wasn't able to start, because it had the wrong version,
1.0.8 in the WEB-INF/lib. The eclipse dependency analysis showed, that
1.0.14 was omitted in conflict with 1.0.8 (why?!).
I thought ok, than i can work with ranges now. I opened the pom of
project A and changed 1.0.8 to 1.0.14 and added a range to it, to
prevent such problems in the future:
<dependency>
<groupId>net.anotheria</groupId>
<artifactId>ano-util</artifactId>
<version>[1.0.14,)</version>
</dependency>
After I rebuilt everything, what do you think I got? 1.0.14? No,
1.0.16-SNAPSHOT ????
Google leads me to this page:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges
which states:
Resolution of dependency ranges should not resolve to a snapshot
(development version) unless it is included as an explicit boundary.
So why am I getting a SNAPSHOT version?
And how can I state that the LATEST RELEASED version is what I
actually want as conflict resolution scenario (isn't it self-evident
actually??).
regards
Leon
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
