It should get ALL transitive dependencies. I'll have to verify that something isn't broken to cause this. As far as I know, there is no difference between a transitive dependency on 1 level or 2, they should all be in the artifacts list. The problem you see could have something to do with the included scopes. Not every scope is transitively handled the same way. Take a look here for the scope resolution: http://maven.apache.org/guides/introduction/introduction-to-dependency-m echanism.html
What would be the use case on the tree? Can you give me an example of how you would expect the tree to look? -----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]
