[
http://jira.codehaus.org/browse/MCOBERTURA-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181005#action_181005
]
Pawel Paprota commented on MCOBERTURA-66:
-----------------------------------------
I can't reproduce this with 2.3-SNAPSHOT.
However, another problem is that in a multi module project the coverage report
does not include tested classes from given module's dependencies that are in
the same project - probably because during test phase there are
non-instrumented classes included on the class path for dependencies.
> Report only shows testes classes
> --------------------------------
>
> Key: MCOBERTURA-66
> URL: http://jira.codehaus.org/browse/MCOBERTURA-66
> Project: Maven 2.x Cobertura Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Hugo Palma
>
> I'm getting this behaviour with the 2.1 release. The 2.0 works fine.
> It seems that if i don't have any tests the report is generated correctly
> with all the packages and classes reporting to have 0% coverage. As i add the
> first test, the report now only show the testes class, all the untested
> classes aren't in the report any more.
--
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
