You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Pankaj Tandon <pa...@gmail.com> on 2008/11/16 15:14:56 UTC
dependency:tree depth
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.
Thanks
Pankaj
[INFO] [dependency:tree]
[INFO] xxx:earthSearch:war:3.4-SNAPSHOT
[INFO] +- xxx:service:jar:3.4-SNAPSHOT:compile
[INFO] | \- xxx:dataAccess:jar:3.4-SNAPSHOT:compile
[INFO] | \- xxx:common:jar:3.4-SNAPSHOT:compile
[INFO] +- junit:junit:jar:3.8.1:test (scope not updated to compile)
[INFO] +- com.lowagie:itext:jar:1.3.1:compile
[INFO] +- org.springframework:spring:jar:1.2.4:compile
[INFO] +- org.springframework:spring-aop:jar:1.2.4:compile
[INFO] | +- org.springframework:spring-beans:jar:1.2.4:compile
[INFO] | | \- org.springframework:spring-core:jar:1.2.4:compile
[INFO] | +- aopalliance:aopalliance:jar:1.0:compile
[INFO] | +- oro:oro:jar:2.0.8:compile
[INFO] | +- commons-pool:commons-pool:jar:1.2:compile
[INFO] | +- commons-attributes:commons-attributes-api:jar:2.1:compile
[INFO] | | +- ant:ant:jar:1.5:compile
[INFO] | | \- qdox:qdox:jar:1.5:compile
[INFO] | +- commons-attributes:commons-attributes-compiler:jar:2.1:compile
[INFO] | | \- com.sun:tools:jar:1.4.2:system
[INFO] | \- com.jamonapi:jamon:jar:1.0:compile
[INFO] +- cglib:cglib-nodep:jar:2.1_2:compile
[INFO] +- commons-lang:commons-lang:jar:2.2:compile
[INFO] +- commons-io:commons-io:jar:1.4:compile
[INFO] +- commons-logging:commons-logging:jar:1.1:compile
[INFO] +- commons-httpclient:commons-httpclient:jar:3.1:compile
[INFO] +- rome:rome:jar:0.9:compile
[INFO] | \- jdom:jdom:jar:1.0:compile
[INFO] +- commons-codec:commons-codec:jar:1.3:compile
[INFO] +- googlebase:googlebase:jar:0.2:compile
[INFO] +- commons-beanutils:commons-beanutils:jar:1.7.0:compile
[INFO] +- log4j:log4j:jar:1.2.9:compile
[INFO] +- struts:struts:jar:1.2.8:compile
[INFO] | +- commons-digester:commons-digester:jar:1.6:compile
[INFO] | \- commons-fileupload:commons-fileupload:jar:1.0:compile
[INFO] +- googlemaps:googlemaps:jar:0.98c-Modified:compile
[INFO] | \- javax.servlet:jsp-api:jar:2.0:compile
[INFO] +- acegisecurity:acegi-security:jar:0.9.0:compile
[INFO] | +- commons-collections:commons-collections:jar:3.1:compile
[INFO] | \- taglibs:standard:jar:1.0.6:compile
[INFO] +- javax.servlet:servlet-api:jar:2.3:compile
[INFO] +- commons-email:commons-email:jar:1.0:compile
[INFO] | +- javax.mail:mail:jar:1.3.3:compile
[INFO] | \- javax.activation:activation:jar:1.0.2:compile
[INFO] +- castor:castor:jar:1.0M1:compile
[INFO] | \- xerces:xercesImpl:jar:2.4.0:compile
[INFO] +- commons-dbcp:commons-dbcp:jar:1.2.1:compile
[INFO] | \- xml-apis:xml-apis:jar:1.0.b2:compile
[INFO] \- quartz:quartz:jar:1.5.2:compile
[INFO]
--
View this message in context: http://www.nabble.com/dependency%3Atree-depth-tp20525672p20525672.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency:tree depth
Posted by Mark Hobson <ma...@gmail.com>.
Also, you can use -Dverbose to display the omitted conflicting dependencies.
Mark
2008/11/16 Pankaj Tandon <pa...@gmail.com>:
>
> Thanks! Makes sense...
>
>
>
> Geoffrey Wiseman wrote:
>>
>> On Sun, Nov 16, 2008 at 9:14 AM, Pankaj Tandon
>> <pa...@gmail.com>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
>>
>>
>
> --
> View this message in context: http://www.nabble.com/dependency%3Atree-depth-tp20525672p20528511.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency:tree depth
Posted by Pankaj Tandon <pa...@gmail.com>.
Thanks! Makes sense...
Geoffrey Wiseman wrote:
>
> On Sun, Nov 16, 2008 at 9:14 AM, Pankaj Tandon
> <pa...@gmail.com>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
>
>
--
View this message in context: http://www.nabble.com/dependency%3Atree-depth-tp20525672p20528511.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency:tree depth
Posted by Geoffrey Wiseman <ge...@gmail.com>.
On Sun, Nov 16, 2008 at 9:14 AM, Pankaj Tandon <pa...@gmail.com>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