[
http://jira.codehaus.org/browse/SUREFIRE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105517
]
Benjamin Bentmann commented on SUREFIRE-257:
--------------------------------------------
surefire and surefire-report are separate JARs, are you sure you use v2.3 of
surefire-report? I just retried your example command-line and had no problems.
Could you append the switch "-X" to enables Maven's debug output and verify it
really states something like
Configuring mojo
'org.apache.maven.plugins:maven-surefire-report-plugin:2.3:report-only'
If you still have an older version, appending the switch "-U" should tell Maven
to search for updates for the plugins (used to execute the current goal).
> surefire-report reruns tests
> ----------------------------
>
> Key: SUREFIRE-257
> URL: http://jira.codehaus.org/browse/SUREFIRE-257
> Project: Maven Surefire
> Issue Type: Bug
> Components: report plugin
> Environment: maven 2.0
> Reporter: Dirk Sturzebecher
> Fix For: 2.4
>
> Attachments: MSUREFIREREP-6-patch.txt
>
>
> 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
