[
http://jira.codehaus.org/browse/SUREFIRE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104603
]
Benjamin Bentmann commented on SUREFIRE-257:
--------------------------------------------
I'm using Maven 2.0.7 and surefire-report-plugin:2.3. From my experience,
"report-only" already works in this version. Mike's problem with the execution
of both "report" and "report-only" should be solved by configuring
surefire-report under the <reporting> section like this:
{code:xml}
<reporting>
...
<plugin>
<artifactId>maven-surefire-report-plugin</artifactId>
...
<reportSets>
<reportSet>
<reports>
<report>report-only</report>
</reports>
</reportSet>
</reportSets>
</plugin>
...
</reporting>
{code}
This seems to be in conformance with
http://maven.apache.org/pom.html#Reporting, one cannot configure a reporting
plugin using the <build> section.
If I type "mvn site", the tests are not run. However, "report-only" still seems
to fork a new lifecycle build. This is not really an issue, but seems
unnecessary, at least to me as a Maven novice.
> 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
