Good Morning Leon I remember running into this failure of version ranges..as recently as ths weekend...it seems that specific version always works fuzzy searches e.g. <version>[1.0.14,2.0)</version> fail so some of the examples displayed here http://mojo.codehaus.org/versions-maven-plugin/examples/resolve-ranges.html do not deliver the version that 'falls' within the specified range..
can you try comma and space delimiter e.g. <version>[2.0.7, 2.0.9)</version> This version-range bug issue was first reported in 2007 http://jira.codehaus.org/browse/MNG-2742 If you are finding consistent failure update the JIRA with a specific testcase at least ONE of us will take a look at this and get the version range resolved Thanks for identifying the bug! Martin Gainty ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Mon, 3 Sep 2012 12:56:15 +0200 > Subject: understanding maven dependencies range > From: [email protected] > To: [email protected] > > 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] >
