[
https://issues.apache.org/jira/browse/MSHARED-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817496#comment-16817496
]
Richard Atkins commented on MSHARED-339:
----------------------------------------
This happens because the default RepositorySession uses a
DependencyGraphTransformer (ConflictResolver) that automatically prunes the
graph to match exactly what Maven resolves dependencies to, using its
nearest-version algorithm. Callers of DependencyGraphBuilder can work around
this by passing a customized DefaultRepositorySession with this transformer set
to null, or set one of the ConflictResolver config properties like
CONFIG_PROP_VERBOSE set to true (as long as the resultant artifact graph isn't
then directly resolved before ignoring the marked duplicate nodes). It seems
roughly as easy for the caller to do this as it is for DependencyGraphBuilder
to do it itself.
> DependencyGraphBuilder does not provide verbose tree
> ----------------------------------------------------
>
> Key: MSHARED-339
> URL: https://issues.apache.org/jira/browse/MSHARED-339
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree-2.1
> Reporter: Paul Gier
> Priority: Major
>
> The dependency graph builder provides a dependency tree which has already
> filtered out duplicate dependencies. In some cases such as testing
> dependency convergence or viewing the verbose dependency tree, it's useful to
> get information about the full tree including duplicates.
> The dependency graph builder should provide an option for including the
> unfiltered dependency tree.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
