[jira] [Created] (MDEP-520) Maven 2 / Maven 3 differences on analyze with cycle

["Jean-Pierre Froud (JIRA)" <ji...@apache.org>]

Jean-Pierre Froud created MDEP-520:
--------------------------------------

             Summary: 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: Question
            Reporter: Jean-Pierre Froud
            Priority: Minor


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}
[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
(v6.3.4#6332)