I have always understood this to mean it is the scope relative to the parent. So if the parent is in test scope its compile dependecies are only dragged into your dependencies of the test scope. So basically the list is resolving that, the tree gives you the full picture to resolve yourself mentally. Am 24.09.2014 16:48 schrieb "Benson Margulies" <[email protected]>:
> 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: [email protected] > For additional commands, e-mail: [email protected] > >
