[Commented] (MDEP-660) Obsolete example of -Dverbose on web page

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Commented] (MDEP-660) Obsolete example of -Dverbose on web page

Konrad Windszus (Jira)

    [ https://issues.apache.org/jira/browse/MDEP-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114784#comment-17114784 ]

Hudson commented on MDEP-660:
-----------------------------

Build succeeded in Jenkins: Maven TLP » maven-dependency-plugin » aether #8

See https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/aether/8/

> 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)