[MDEP-520] Maven 2 / Maven 3 differences on analyze with cycle

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Labels: S2
• Assignee: Unassigned
• Reporter: Jean-Pierre Froud
• Created: 01/Mar/16 12:41
• Updated: 28/Aug/22 12:14
• Resolved: 28/Aug/22 12:14

Description

Here's the dependency tree I'm using:

[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

As you can see, there's a cycle : PA > PC > PA

Using maven 2.2.1:

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

Using maven 3.3.3:

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

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?