You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2020/07/17 15:37:00 UTC
[jira] [Updated] (MDEP-520) Maven 2 / Maven 3 differences on
analyze with cycle
[ https://issues.apache.org/jira/browse/MDEP-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold updated MDEP-520:
---------------------------------------
Labels: S2 (was: )
> Maven 2 / Maven 3 differences on analyze with cycle
> ---------------------------------------------------
>
> Key: MDEP-520
> URL: https://issues.apache.org/jira/browse/MDEP-520
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Reporter: Jean-Pierre Froud
> Priority: Minor
> Labels: S2
>
> Here's the dependency tree I'm using:
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Building PA 0.0.2-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ PA ---
> [INFO] myTest:PA:jar:0.0.2-SNAPSHOT
> [INFO] \- PC:PC:jar:0.0.1-SNAPSHOT:compile
> [INFO] \- myTest:PA:jar:0.0.1-SNAPSHOT:compile
> {code}
> As you can see, there's a cycle : {{PA > PC > PA}}
> Using maven 2.2.1:
> {code}
> mvn dependency:analyze
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Unnamed - myTest:PA:jar:0.0.2-SNAPSHOT
> [INFO] task-segment: [dependency:analyze]
> [INFO] ------------------------------------------------------------------------
> ...
> [INFO] No dependency problems found
> {code}
> Using maven 3.3.3:
> {code}
> mvn dependency:analyze
> [INFO] ------------------------------------------------------------------------
> [INFO] Building PA 0.0.2-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> ...
> [INFO] --- maven-dependency-plugin:2.8:analyze (default-cli) @ PA ---
> [WARNING] Used undeclared dependencies found:
> [WARNING] myTest:PA:jar:0.0.1-SNAPSHOT:compile
> {code}
> The analyze in maven 3 wants me to add {{PA}} as a dependency to {{PA}}, to itself. Is it possible to have the same behavior as maven 2 using maven 3?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)