Maven 2&3依赖关系的差异:循环分析

Question

下面是我使用的依赖树：

[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

正如你所看到的，有一个循环：

PA > PC > PA

使用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

使用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

使用maven 3的分析要求我将PA作为一个依赖项添加到PA中。是否可以使用maven 3具有与maven 2相同的行为？

Answer 1

下面是我使用Maven 3获得与Maven 2相同的结果的解决方法：

<build>
    <pluginManagement>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
                <configuration>
                    <ignoredDependencies>
                        <ignoredDependencie>${project.groupId}:${project.artifactId}::</ignoredDependencie>
                    </ignoredDependencies>
                </configuration>
            </plugin>
        </plugins>
    </pluginManagement>
</build>