You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:23:27 UTC
[jira] (MPJCOVERAGE-36) Coverage report showing more than 100%
coverage for few packages/classes
[ https://jira.codehaus.org/browse/MPJCOVERAGE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MPJCOVERAGE-36.
-------------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
> Coverage report showing more than 100% coverage for few packages/classes
> ------------------------------------------------------------------------
>
> Key: MPJCOVERAGE-36
> URL: https://jira.codehaus.org/browse/MPJCOVERAGE-36
> Project: Maven 1.x JCoverage Plugin
> Issue Type: Bug
> Affects Versions: 1.0.5
> Reporter: Yogesh
>
> The Coverage report is showing more than 100% coverage for few packages. Some of the files are indicating coverage of over 140%. I am not able to debug the issue so far.
> I have report generated for two projects and I merge their jcoverage.ser files with the one generted on server after Junit execution. The report statistics appeared correct some time back and look very doubtful to me now.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)