[
https://issues.apache.org/jira/browse/MSHARED-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372610#comment-17372610
]
Robert Scholte commented on MSHARED-788:
----------------------------------------
Currently things that are filtered out with a DependencySelector cannot be
added to the tree, because it simply implements {{boolean selectDependency(
Dependency dependency )}} without the option to add information to a verbose
tree. Ideally I would be able to see all dependencies as specified in the
matching pom and see why things are not part of the tree. For test-scoped
dependencies this most likely not an issue, but it would be great if you could
see that a dependency was removed by exclusion of an ancestor (and which
ancestor).
Same counts for cyclic dependencies, but these are already filtered out by
embedded code (that behaves like a DependencySelector), so again no way to add
this information to the verbose tree without changes to Maven Artifact Resolver.
With that in mind, we can clean up the expected verbose tree.
> Add functionality to collect raw dependencies in Maven 3+
> ---------------------------------------------------------
>
> Key: MSHARED-788
> URL: https://issues.apache.org/jira/browse/MSHARED-788
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree-3.0, maven-dependency-tree-3.0.1
> Reporter: Gabriel Belingueres
> Assignee: Robert Scholte
> Priority: Major
> Fix For: maven-dependency-tree-3.1.0
>
> Time Spent: 10m
>
> Add funcionality allowing to collect raw project dependencies. Add a layer to
> hide against Maven 3's sonatype aether and Maven 3.1+ eclipse aether.
> This could be used to implement dependencyConvergence and
> requireUpperBoundDeps enforcer rules.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
