[ http://jira.codehaus.org/browse/MSUREFIREREP-6?page=comments#action_79032 ] Sasha A commented on MSUREFIREREP-6: ------------------------------------
The workaround I've been using is the problem Peter Anning has above is the following. First I run a target that invokes the tests, like: mvn test OR mvn install Then, if the tests fail, I run: mvn -Dmaven.test.skip=true surefire-report:report OR mvn -Dmaven.test.skip=true site Either of these commands runs the surefire report goal without running the tests again. Obviously, this is just a workaround, and it doesn't work well for continuous integration systems that need to run everything automagically, but it has helped me a lot. > surefire-report reruns tests > ---------------------------- > > Key: MSUREFIREREP-6 > URL: http://jira.codehaus.org/browse/MSUREFIREREP-6 > Project: Maven 2.x Surefire report Plugin > Issue Type: Bug > Environment: maven 2.0 > Reporter: Dirk Sturzebecher > > surefire-report reruns the tests. In my case this is not just annoying, but > leads to a failure, as the VM (probably) is reused and leftovers from the > first tests are (definitly) still present. > I run maven with: clean package site -- 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
