Brett Porter wrote:
Does that just mean some plugins need to be locked down to their
non-latest equivalent in the reactor build, so you aren't using what you
are building?
Actually, that should already be the case unless I am something missing.
To reproduce the issue, simply add the snippet
<profiles>
<profile>
<id>run-its</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
</plugin>
</plugins>
</build>
</profile>
</profiles>
to the POM of maven-invoker-plugin and run "mvn validate -P run-its" on
maven-plugins. This gives the following build failure:
The projects in the reactor contain a cyclic reference:
Edge between
'Vertex{label='org.apache.maven.plugins:maven-invoker-plugin'}'
and
'Vertex{label='org.apache.maven.plugins:maven-antrun-plugin'}'
introduces to cycle in the graph
org.apache.maven.plugins:maven-antrun-plugin -->
org.apache.maven.plugins:maven-invoker-plugin -->
org.apache.maven.plugins:maven-antrun-plugin
My personal impression is that the plugin versions are not properly
considered. Starting at the POM for AntRun, we get the edge
maven-antrun-plugin:1.3-SNAPSHOT -->
maven-invoker-plugin:1.2.1-SNAPSHOT
Moving on to the Invoker POM, the next edge is
maven-invoker-plugin:1.3-SNAPSHOT -->
maven-antrun-plugin:1.2
so the artifacts involved are clearly different.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
