[
http://jira.codehaus.org/browse/MCLOVER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94704
]
Indrajit Khare commented on MCLOVER-70:
---------------------------------------
I noticed this recently as well. Using the maven-clover-plugin does not give
comprehensive coverage numbers. For projects that have modules that are
dependent transitively non-clovered jars are being used for the dependencies
when running tests in clover:instrument.
> Non-Clovered Jars used for Transitive Dependencies
> --------------------------------------------------
>
> Key: MCLOVER-70
> URL: http://jira.codehaus.org/browse/MCLOVER-70
> Project: Maven 2.x Clover Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: James Olsen
>
> When executing tests or building ear/war archives, the plugin is not using
> instrumented jars for transitive dependencies. The ordinary jar is used
> instead. Hence no test coverage stats are obtained for those components.
> Adding the transitive dependency as a direct dependency on the project
> results in both the instrumented and plain jar appearing in the archive. I
> presume the same also happens for the unit test classpath although I haven't
> confirmed.
> The plugin should use the instrumented version of the jar where available
> regardless of whether the dependency is direct or transitive.
--
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
