[
http://jira.codehaus.org/browse/MCOBERTURA-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125903
]
Giridhar Nandigam commented on MCOBERTURA-70:
---------------------------------------------
I had the same above problem and the following workaround worked for me:
-- I set the configuration on the maven-surefire-plugin to start in forkmode.
<configuration>
<forkMode>once</forkMode>
</configuration>
Can somebody verify this?
Thanks,
Giri
> 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
