[
http://jira.codehaus.org/browse/MCOBERTURA-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MCOBERTURA-40.
------------------------------------
Resolution: Not A Bug
Assignee: Robert Scholte
The surefire-plugin puts first the testOutputDirectory on it's classpath,
followed by the outputDirectory and as you should know: first find wins.
The instrumented classes end up in a new outputDirectory, redefined by the
cobertura-m-p to target/generated-classes/cobertura, so the instrumented
classes won't be used while running the unit tests. That's why you got your 0%;
> Same outputDirectory and testOutputDirectory fails to report coverage
> ---------------------------------------------------------------------
>
> Key: MCOBERTURA-40
> URL: http://jira.codehaus.org/browse/MCOBERTURA-40
> Project: Maven 2.x Cobertura Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Windows XP, Maven 2.0.4
> Reporter: Allan Shoup
> Assignee: Robert Scholte
> Attachments: cobertura-test.zip
>
>
> When I define the build output directory and test output directory to be the
> same thing, the Cobertura plugin reports 0% coverage. Attached is a simple
> project which demonstrates the problem. Just extract and run "mvn site". When
> the coverage report is generated, 0% is reported. When you edit the POM and
> comment out the
> <outputDirectory>bin</outputDirectory>
> <testOutputDirectory>bin</testOutputDirectory>
> lines, it will correctly report 67% coverage.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
