[
https://jira.codehaus.org/browse/MDEP-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MDEP-443.
------------------------------
Resolution: Fixed
Fix Version/s: 2.9
Assignee: Herve Boutemy
documentation updated and warning added in
[r1588916|http://svn.apache.org/r1588916]
> dependency tree should be the same when using verbose or not
> ------------------------------------------------------------
>
> Key: MDEP-443
> URL: https://jira.codehaus.org/browse/MDEP-443
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: tree
> Reporter: Cintia DR
> Assignee: Herve Boutemy
> Priority: Minor
> Fix For: 2.9
>
>
> 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|https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-AutomaticPluginVersionResolution]:
> {code}
> 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 );
> }
> {code}
> It's very misleading. Even the
> [documentation|http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html#verbose]
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
