I think this is a maven bug. Since it hits the cyclic dom4j, it completely stops including all the rest of jaxen dependencies. I removed the dom4j in my local repo from the jaxen jar, and everything including xom,xerces etc (the rest of the jaxen depends) are included.
dom4j:dom4j:jar:1.5.2 (selected for compile) [DEBUG] stax:stax-api:jar:1.0 (selected for compile) [DEBUG] pull-parser:pull-parser:jar:2 (selected for compile) [DEBUG] jaxme:jaxme-api:jar:0.3 (selected for compile) [WARNING] This artifact has been relocated to xml-apis:xml-apis:1.0.b2. [DEBUG] xml-apis:xml-apis:jar:1.0.b2 (selected for compile) [DEBUG] msv:xsdlib:jar:20030807 (selected for compile) [DEBUG] xpp3:xpp3:jar:1.1.3.3 (selected for compile) [DEBUG] dom4j:dom4j:jar:1.5.2 (removed - causes a cycle in the graph) [DEBUG] jaxen:jaxen:jar:1.1-beta-4 (selected for compile) [DEBUG] msv:relaxngDatatype:jar:20030807 (selected for compile) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, January 07, 2006 11:38 PM To: Maven Users List Subject: RE: [m2] dependency-plugin: Doesn't copy transitive dependencies deeper than first level Brian, I actually did the test with dom4j 1.6 (not jdom as I mentioned - I always confuse those two). The dom4j 1.6 POM has a dependency on Jaxen specified as: <dependency> <groupId>jaxen</groupId> <artifactId>jaxen</artifactId> <version>1.1-beta-4</version> </dependency> Jaxen 1.1-beta-4 has a dependency in the POM for XOM: <dependency> <groupId>xom</groupId> <artifactId>xom</artifactId> <version>1.0b3</version> </dependency> But xom isn't copied over to target/dependency in my case. One thing which is funny in my test case though is that Jaxen 1.1-beta-4 has a dependency declared on dom4j 1.5.2 (kinda circular dependency): <dependency> <groupId>dom4j</groupId> <artifactId>dom4j</artifactId> <version>1.5.2</version> </dependency> Could that be causing an issue and make my test case invalid? Chris "Brian E. Fox" <[EMAIL PROTECTED]> wrote: I just verified with a local project, it is going much deeper than 1 level. I looked at the jdom pom...the jaxen dependency is optional. Optional means don't transitively include, so any project including jdom shouldn't get jaxen and thus anything jaxen includes. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, January 07, 2006 11:08 PM To: [email protected] Subject: [m2] dependency-plugin: Doesn't copy transitive dependencies deeper than first level If I'm not wrong, then the dependency-plugin doesn't copy transitive dependencies deeper than the first level (which are dependencies of dependencies of dependencies). For example: jdom has a dependency on jaxen which has a dependency on xom. A test project now has a dependency for jdom specified with scope compile. In that case I do not get xom copied into target/dependency. Is there a way to configure the plugin so that it copies dependencies on all levels? At last, I wish the plugin could be configured so that the dependencies could be copied into a tree rather than just as flattened tree. Anybody any hint? Thanks, Chris --------------------------------------------------------------------- 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]
