Then you need to add commons-collections as a "direct dependency". And "lock down" the version.
Maven does its best to sort out the dependency graphs including transitivity etc. But sometimes it needs your help. This seems to be one of those times. Wayne On 9/7/07, Farhdine Boutzakhti <[EMAIL PROTECTED]> wrote: > Hi Wayne! > > I can't try this, because the conflict is in a sub-dependency, it isn't > a direct dependency. > > Thanks for your help. > > Farhdine. > > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Friday, September 07, 2007 4:11 PM > To: Maven Users List > Subject: Re: Dependencies conflict with dependencyManagement > > Try "locking down" the version you've declared in depMgmt like: > > <dependency> > <groupId/> > <artifactId/> > <version>[3.1]</version> > </dependency> > > With this configuration, you should be more or less "guaranteed" to > get 3.1 in your Jars etc. > > Wayne > > On 9/7/07, Farhdine Boutzakhti <[EMAIL PROTECTED]> wrote: > > Hi all! > > > > > > > > I've a question about dependencies conflict management. > > > > > > > > I have a POM with sub-modules. > > > > I have specified my dependencies in a dependencyManagement tag. > > > > All sub-modules include the dependencies without version and scope. > > > > > > > > Here is my problem: > > > > My sub-modules generate WAR archives without JAR libraries. Only the > > Manifest file is generated with the dependencies. > > > > At the end of my parent POM, I generate an EAR file with all the WAR > > files and all the libraries. > > > > > > > > I've seen in the EAR that each WAR file includes in its Manifest a > > different version of commons-collections (3.1, 2.1, 2.1.1). > > > > But, the EAR includes only one of them: the 2.1 version. > > > > > > > > Why Maven doesn't include the 3.1 version, and why each Manifest is > > different? > > > > How can I resolve this issue? > > > > > > > > Can anyone help me, please? > > > > > > > > Thanks, > > > > > > > > Farhdine Boutzakhti > > > > Calyon CIB / Capital Markets > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
