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

Maarten Mulders commented on MDEP-666:
--------------------------------------

Invalid for the latest version of the Dependency plugin. It appears I was using 
an older version :(.

> dependency:tree does not work for multi-module project
> ------------------------------------------------------
>
>                 Key: MDEP-666
>                 URL: https://issues.apache.org/jira/browse/MDEP-666
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: tree
>         Environment: Both macOS and Linux.
>            Reporter: Maarten Mulders
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In a multi-module project, {{mvn dependency:tree}} does not work unless
>  # the project has been installed to the local repository, or
>  # the project has been deployed to a remote repository, or
> # run it as {{mvn compile dependency:tree}}
> In a project that was never installed or deployed, the Mojo will fail to 
> print a dependency tree even when all dependencies are resolvable.
> I have a [sample project on 
> GitHub|https://github.com/mthmulders/maven-multimodule-dependency-tree] that 
> illustrates this.
> The _child-3_ module depends on _child-2_ (part of the reactor). The 
> _child-2_ module depends on _child-1_ (also part of the reactor) and some 
> dependencies that are deployed to Maven Central. The _child-1_ module only 
> has dependencies to external artifacts which can be found in Maven Central.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to