Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.11.2
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:windows XP/cygwin
maven 1.1
maven-junit-report-plugin 1.5.1
-
Testcase included:yes
-
Number of attachments :
Description
Running the clover report as the only project report to obtain source lines of code works with the property maven.clover.instrument.tests set = true.
However, if the project also specifies the junit report (<report>maven-junit-report-plugin</report>), then the clover report will not include test lines of code, even with the property maven.clover.instrument.tests=true.
I looked at the junit-report-plugin plugin.jelly, put nothing jumped out at me as being suspect along the lines of modifying maven.test.compile.src.set, for example.
This is can reproduced by adding the <report>maven-junit-report-plugin</report> to the existing clover plugin test case:
testSiteReportAndGenerationOfDifferentFormats
Additional info...swapping the order of the reports in the <reports> section of project.xml is a workaround for this problem.
To reproduce this behaviour, using the testSiteReportAndGenerationOfDifferentFormats test case:
Causes the issue initially raised by this JIRA:
=====
<reports>
<report>maven-junit-report-plugin</report>
<report>maven-clover-plugin</report>
</reports>
This works as expected:
=====
<reports>
<report>maven-clover-plugin</report>
<report>maven-junit-report-plugin</report>
</reports>
Jeff