In spite of Jason's sage advice, I am about to commit a change to a
historical IT. I can't see what else to do. The IT seems simply
broken, and I am stumped for an explanation of why it was passing on
Jenkins until this afternoon. It never passed on either of my local
systems.
The test is the test for mng-3746.
This IT consists of two projects. One builds a plugin, one uses it.
First, the plugin-building project lacks the execution to instruct the
stub install plugin to actually install anything. Second, and more
strange yet, they disagree on the plugins's artifactid! Note that the
reactor isn't involved; the test invokes the maven command line twice:
once to build the plugin, once to use it.
Here's the diff of the fix to that:
===================================================================
--- src/test/resources/mng-3746/project/pom.xml (revision 1212869)
+++ src/test/resources/mng-3746/project/pom.xml (working copy)
@@ -14,7 +14,7 @@
<plugins>
<plugin>
<groupId>org.apache.maven.its.mng3746</groupId>
- <artifactId>maven-mng3746-plugin</artifactId>
+ <artifactId>mavenit-mng3746-plugin</artifactId>
<version>1</version>
<executions>
<execution>
And the pom that builds the plugin does contain:
<artifactId>mavenit-mng3746-plugin</artifactId>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
