[
http://jira.codehaus.org/browse/MCOBERTURA-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105099
]
Gary Kind commented on MCOBERTURA-70:
-------------------------------------
I have tried moving back to 1.7 and it still does not work. AND we cannot run
it twice because that does not work either. It does not work because we have 2
projects which need cobertura reports and both are run from a parent pom.
Running mvn cobertura:cobertura twice from the parent does not work! We
literally have to do a changedir (cd) to each project and run it twice -- which
defeats the purpose of a build environment. We need some kind of fix for this
ASAP. C'mon, it can't be that hard to fix. If it is, then Cobertura really
has something wrong architecturally.
> I must run 'mvn cobertura:cobertura' twice to get a valid coverage report.
> --------------------------------------------------------------------------
>
> Key: MCOBERTURA-70
> URL: http://jira.codehaus.org/browse/MCOBERTURA-70
> Project: Maven 2.x Cobertura Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Gary Kind
>
> Our nightly build does:
> 'mvn clean'
> 'mvn install'
> 'mvn cobertura'
> 'mvn site'
> We have found that for the last couple of months (or possibly more), our
> coverage reports are showing 0% coverage on all tests. I have found that we
> have to run 'mvn cobertura:cobertura' TWICE! to get a valid coverage report.
> What gives? Is there any workaround? I have tried all sorts of things but
> nothing really works.
--
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
