There are a few ways: mvn -X will give you the debug output and will show the transitive that are brought in by the main dependencies, though I found this to be a bit tricky to use...my preferred way is too find the jars in my project(s) that mvn bundles a pom.xml in...if you look ar the pom.xmls in these jars you will find the dependencies they are bringing in....you then need to declare the jar as a dependency in the pom.xml in the particular artifact you want this excluded in and add <excludes><excludes>...place only groupId and artifactId inside here...</exclude></excludes> inside the dependency declaration or you can add the tag in the jar plugin config that excludes the pom.xml if you have control over the build...then you dont have to worry about this stuff
On 8/25/07, Larry Suto <[EMAIL PROTECTED]> wrote: > There are a few ways. mvn -X will give you debug output > > On 8/25/07, EN <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > We have a multi module project: > > parent - pom, dependencyManagement > > proj1 - jar > > proj2 - jar > > proj3 - war > > > > Although we use log4j 1.2.14, our proj3.war file contains log4j 1.2.12 which > > probably added by maven as transitive dependency of one of our dependencies > > (activemq-parent-4.1.1.pom or commons-logging-1.1.pom). > > > > How can I force maven to package only log4j 1.2.14? > > > > Thanks, > > Erez. > > -- > > View this message in context: > > http://www.nabble.com/Control-transitive-dependencies-tf4330206s177.html#a12332508 > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > 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]
