[
https://issues.apache.org/jira/browse/MDEP-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17097558#comment-17097558
]
Karl Heinz Marbaise commented on MDEP-660:
------------------------------------------
Done in
[6adc71cceb0cc8bfc05d0b6d1ff72652d7e39f33|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commitdiff;h=6adc71cceb0cc8bfc05d0b6d1ff72652d7e39f33]
> Obsolete example of -Dverbose on web page
> -----------------------------------------
>
> Key: MDEP-660
> URL: https://issues.apache.org/jira/browse/MDEP-660
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: tree
> Affects Versions: 3.1.1
> Environment: Web - Chrome
> Reporter: Larry West
> Assignee: Karl Heinz Marbaise
> Priority: Minor
> Labels: documentation
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The
> [examples/resolving-conflicts-using-the-dependency-tree|https://maven.apache.org/plugins/maven-dependency-plugin/examples/resolving-conflicts-using-the-dependency-tree.html]
> page offers hope that John Lin has worked on MDEP-644:
> ----
> {quote}
> h2. Resolving conflicts using the dependency tree
> A project's dependency tree can be expanded to display dependency conflicts.
> For example, to find out why Commons Collections 2.0 is being used by the
> Maven Dependency Plugin, we can execute the following in the project's
> directory:
> # mvn dependency:tree -Dverbose -Dincludes=commons-collections
> The {{verbose}} flag instructs the dependency tree to display conflicting
> dependencies that were omitted from the resolved dependency tree. In this
> case, the goal outputs:
> ...
> {quote}
> ----
>
> Alas, it is not so, as MDEP-374 explains.
> That page should perhaps be deleted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
