[ http://jira.codehaus.org/browse/MSUREFIREREP-6?page=comments#action_65263 ]
Pascal Magnard commented on MSUREFIREREP-6: ------------------------------------------- I've got the same issue as Dirk. I added the surefire-report plugin declaration to the reporting section of my pom and each time this plugin is executed, the test phase is invoked. The expected behavior, according to the documentation, would be the surefire plugin to invoke the test phase (http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html) but not the surefire-report plugin (http://maven.apache.org/plugins/maven-surefire-report-plugin/report-mojo.html). Having the tests ran twice when invoking mvn clean install site is more than annoying for the project i'm working on because the compilation and the testing are performed twice and they unfortunatly take a big while. That would be great if you could provide a mean to prevent from having the surefire-report plugin kicking off a test phase when triggered. Some boolean like 'invokeTest' in the <configuration> section of the plugin would be just fine. (And btw, Brett, i've been looking for you solution but was not able to find any <skip> tag in either the Maven 1.1 or Maven 2 POM XML schema.) > surefire-report reruns tests > ---------------------------- > > Key: MSUREFIREREP-6 > URL: http://jira.codehaus.org/browse/MSUREFIREREP-6 > Project: Maven 2.x Surefire report Plugin > 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
