Thank's Brett. I read over these passage. Using the newer library versions can be forced by defining it in the projects' pom.
-chris Am Montag, 6. März 2006 15:53 schrieb Brett Porter: > nearer != newer. > > It resolves the one closest to your pom in the dependency graph. > > http://maven.apache.org/guides/introduction/introduction-to-dependency-mech >anism.html > > Maven 2.1 will provide a newer resolver. It can be achieved in Maven > 2.0 by using ranges. > > - Brett > > On 3/7/06, Christian Mouttet <[EMAIL PROTECTED]> wrote: > > sorry I forgot something > > > > > Hi, > > > > > > how does the dependency management handle equals artifacts with > > > different versions? I thought that the newer version wins but following > > > part of my 'maven -X'-log shows: > > > > > > [DEBUG] commons-collections:commons-collections:jar:2.1 (removed > > > - nearer found: 2.1.1) > > > > > > Maybe the sorting of version numbers with different lengths doesn't > > > work properly. > > > > I'm bundling a web application and I can find commons-collections-2.1.jar > > in WEB-INF/lib. That's what I don't understand. > > > > > Regards > > > > > > -chris ********************************************************************** Diese E-Mail wurde auf Viren ueberprueft. [EMAIL PROTECTED] ********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
