I'm suffering from SUREFIRE-30, which is down to the fact that the cobertura
plugin uses
surefire-booter-1.5.2.jar - which has this problem.
I have tried adding a different booter into the plugin :
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
<version>2.0-SNAPSHOT</version>
<executions>
<execution>
<goals>
<goal>clean</goal>
</goals>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.apache.maven.surefire</groupId>
<artifactId>surefire-booter</artifactId>
<version>1.5.3-SNAPSHOT</version>
</dependency>
</dependencies>
</plugin>
But mvn -X shows it's still using the 1.5.2 jar:
[DEBUG] Adding to surefire test classpath: C:\Documents and
Settings\nigel.magney\.m2\repository\org\apache\maven\surefire\surefire\1.5
.2\surefire-1.5.2.jar
Short of recompiling all these dependent files (& having to distribute them
internally so everyone else's build works) is there a way of overriding this
behaviour ?