Hi,
Some users of the maven-clover2-plugin are complaining that when they
run their build with clover, it fails because some transitive
dependencies which have been excluded in the <dependency> definition
are being added to the compile time classpath.
The offending code is on line #367 here:
http://svn.atlassian.com/fisheye/browse/public/contrib/clover/maven-clover-plugin/trunk/src/main/java/com/atlassian/maven/plugin/clover/CloverInstrumentInternalMojo.java?r=24080#l353
Set set = new HashSet( getProject().getDependencyArtifacts() );
set.add( cloverArtifact );
getProject().setDependencyArtifacts( set );
This is a work around for http://jira.codehaus.org/browse/MNG-2197 ,
trying to ensure that clover is on the compile time classpath.
Is there a better way to implement this? Is it possible to filter the
exclusions from the set of dependencyArtifacts?
Cheers,
Nick Pellow
