[ http://jira.codehaus.org/browse/MOJO-271?page=comments#action_57799 ]
Mike Perham commented on MOJO-271: ---------------------------------- That's the entire output. There's no root failure printed anywhere, even with -X. I am not forking my tests. Ah, here's some interesting behavior. Delete your cobertura.ser and run then cobertura:cobertura twice. The first cobertura run will produce a 0% report I think *because it doesn't write data until the VM exits*. The second run will run the tests again but I believe the report is based on the data from the first run, as the data from the second run has not been emitted to disk yet. I think this is the crux of much of the odd behavior people have been seeing with Cobertura. And with that said, now I can't reproduce surefire running twice. > Cobertura runs tests twice > -------------------------- > > Key: MOJO-271 > URL: http://jira.codehaus.org/browse/MOJO-271 > Project: Mojo > Type: Bug > Components: cobertura > Versions: 2.0-beta-1 > Reporter: Mike Perham > Fix For: 2.0-beta-1 > > > The lifecycle.xml specifies a test goal but apparently this is redundant and > the second execution immediately fails the build. The standard forked > lifecycle already contains a test goal. If I just comment the entire block > out, it works as expected. -- 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
