I have a multi module project. I am using Clover to generate reports and to find out the code coverage. I have my test in ModuleA which has a dependency on ModuleB. I am using this command to generate the reports:
mvn clean compile clover:instrument clover:aggregate clover:clover -P all
All the tests run fine but when I check the code coverage in ModuleB it's zero and the coverage has been reported only for classes inside ModuleA. Am I missing something here?
This is the config in root pom.
<plugin>
<groupId>org.openclover</groupId>
<artifactId>clover-maven-plugin</artifactId>
<version>4.3.1</version>
</plugin>
<profile>
<id>all</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>B</module>
<module>A</module>
</modules>
</profile>
Please try:
mvn clean clover:instrument clover:aggregate clover:clover -P all
or
mvn clean clover:setup verify clover:aggregate clover:clover -P all
I suspect that calling 'compile' and next 'instrument' caused that Clover forked a parallel build cycle in which it took a non-instrumented jar from the second module. But I'd have to see build logs to be sure.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.