The cobertura-maven-plugin uses @execute to run a parallel lifecycle for 'test'.
A bug report claims that, in maven 3, this fails for them, because the
surefire forkMode is ignored.
Is there something new in M3 that I need to add to the plugin? Is this
perhaps an M3 bug?
The relevant mojo config in cobertura is:
@execute phase="test" lifecycle="cobertura"
The lifecycle def is:
<lifecycles>
<lifecycle>
<id>cobertura</id>
<phases>
<phase>
<id>process-classes</id>
<executions>
<execution>
<goals>
<goal>instrument</goal>
</goals>
</execution>
</executions>
</phase>
<phase>
<id>test</id>
<configuration>
<classesDirectory>${project.build.directory}/generated-classes/cobertura</classesDirectory>
<testFailureIgnore>true</testFailureIgnore>
<forkMode>once</forkMode>
</configuration>
</phase>
</phases>
</lifecycle>
</lifecycles>
In case anyone cares the report can be found here:
http://jira.codehaus.org/browse/MCOBERTURA-132
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
