This is the first time I see that a plugin transitive dependency makes it into the final artifact. What versions of maven and the maven-war-plugin are you using?
With regards, Nick Stolwijk -----Original Message----- From: amit kumar [mailto:[EMAIL PROTECTED] Sent: Thu 1/31/2008 11:56 AM To: Maven Users List Subject: Re: Dependency resolution of maven-war-plugin Yes Felix maven-war-plugin does include the transitive dependencies. For a transitive dependency of a plugin, the way(workaround) I found and using is to declare that dependency explicitly in your pom.xml and declare it to be available at only compile time ( <scope> tag). For the transitive dependencies of the rest of the dependencies I am using <exclusion> tag with in the dependency tag. That probably be not the sanest way of it, but this was what I could find out with the help of other maven users here on the list. Amit On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]> wrote: > Hello > > I have a question re dependency resolution of the maven-war-plugin. > If I run 'mvn install' a war is built including the library xbeans.jar > (xmlbeans:xbean is a transitive dependency of a plugin). Why is this > dependency included though not declared? > > A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns > with no result. It seems to me that maven-war-plugin includes also > transitive plugin dependencies. > > Thanks for your help, Felix > > > --------------------------------------------------------------------- > 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]
