On Sun, Nov 16, 2008 at 9:14 AM, Pankaj Tandon <[EMAIL PROTECTED]>wrote:
> > Hello all, > I was wondering how the dependency:tree mojo decides how deep it should go > to list dependencies? > > For example, in the following output, why does it stop at > org.springframework:spring-core:jar:1.2.4:compile and not go deeper. There > are no parameters also to configure this. (using help:describe, haven't > looked at the source) > > Either it should have stopped at one transitive dependency deep or gone all > the way. Not sure what the rationale for the 3 deep I see here is. > It goes 'all the way', but when Maven finds an artifact/group at a higher level and a lower level, it prunes the lower level dependency -- assuming the "higher level" is closer to importance by being closer to your project, I guess? So all the dependencies that spring-core 1.2.4 depends on (commons-collections, commons-logging, servlet) are also listed at higher levels in your POM and have been pruned from the dependency tree, which accurately reflects how Maven will retrieve the dependencies as well. - Geoffrey -- Geoffrey Wiseman
