-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 2.5
-
Component/s: None
-
None
Hi,
I would like to use clover to generate war files with all its dependencies instrumented. I mean
war1 composed by jar1-clover, jar2-clover etc...
So I tried to use the clover2:setup goal starting from your multimodule project sample on the svn repository.
I changed the instrument goal by the setup goal
However the jars deployed on my local repository (and used for the building of the war) are not the clovered jars as I thought it should.
Could you tell me if my comprehension of clover2:setup is wrong or not ? This goal should swap the sources to the instrumented sources so that all next tasks will use instrumented code ?
If I'm right, it should install the instrumented jar on my repository however it don't work.
I've attached a sample project for that.
Try the following command :
mvn clean install -Dmaven.test.skip -o
You'll see that installed jars are not the clovered jars.
Here is the configuration of the plugin :
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<fork>false</fork>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
<plugin>
<groupId>com.atlassian.maven.plugins</groupId>
<artifactId>maven-clover2-plugin</artifactId>
<version>2.5.0</version>
<configuration>
<flushPolicy>threaded</flushPolicy>
<flushInterval>100</flushInterval>
<licenseLocation>${clover.licenseLocation}</licenseLocation>
</configuration>
<executions>
<execution>
<id>main</id>
<phase>verify</phase>
<goals>
<goal>setup</goal>
<goal>aggregate</goal>
<goal>check</goal>
<goal>log</goal>
</goals>
</execution>
<execution>
<id>site</id>
<phase>pre-site</phase>
<goals>
<goal>instrument</goal>
<goal>aggregate</goal>
<!-- We save a history point in order to have data to generate a historical report -->
<goal>save-history</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
Could you tell me how to make it works ?
