maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé BOUTEMY <>
Subject Re: What does it mean when dependency:list and dependency:tree disagree on scope?
Date Thu, 25 Sep 2014 06:24:32 GMT
probably a bug in dependency:tree

dependency:list just displays info directly taken from Maven core: you can 
trust it

dependency:tree does a lot of logic to track resolution, with different 
implementations for Maven 2, 3.0.x and 3.1+: at the moment, I had a lot of 
work to be sure that conflicts were well detected, but I never checked scopes 
(checking conflicts was already a hard task)

so please open a bug report for dependency:tree/shared/maven-dependency-tree
and we'll need to work back on Maven 3.0.x and 3.1+ implementations



Le mercredi 24 septembre 2014 10:47:47 Benson Margulies a écrit :
> I've got a project where (a) we went to a lot of trouble to make sure
> that log4j was scoped to test, (b) dependency:list shows it as
> scope=test, (c) dependency:tree shows it as scope=compile, using the
> most recent dependency plugin and maven 3.0.5.
> The path to log4j is through slf4j-log4j, which dependency:analyze
> thinks is 'unused'.
> here is the confusing output of :tree:
>  +- org.slf4j:slf4j-log4j12:jar:1.6.3:test
>  |  \- log4j:log4j:jar:1.2.16:compile
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message