Description
When running dependency tree (version 2.8) using maven 3, the generated tree is consistent with what maven is using.
If you enable -Dverbose, I have a maven 2 dependency tree:
if ( verbose ) { // verbose mode force Maven 2 dependency tree component use dependencyTreeString = serializeVerboseDependencyTree( dependencyTreeBuilder.buildDependencyTree( project, localRepository, artifactFilter ) ); } else { // non-verbose mode use dependency graph component, which gives consistent results with Maven version // running rootNode = dependencyGraphBuilder.buildDependencyGraph( project, artifactFilter ); dependencyTreeString = serializeDependencyTree( rootNode ); }
It's very misleading. Even the documentation doesn't mention it.
Probably there's a good reason to not use Aether for the verbose mode, but I guess at least it should print a warning at the end of the process and explicitly say it in the documentation.