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]
