|
[
Permalink
| « Hide
]
Brice Copy added a comment - 17/Aug/06 04:36 AM
Is there a workaround for this, like using an older version of surefire ?
I'd suggest raising the Priority from Minor to Major.
It may be just a presentation issue, but frankly it's quite annoying to see all the HTML reports incorrect, even for all the Maven plugins themselves http://maven.apache.org/plugins/maven-install-plugin/surefire-report.html My workaround is to use <forkMode>always</forkMode> in the surefire plugin config of the POM. Slows things down a bit, but at least the reports are coherent.
With workaround
<forkMode>always</forkMode> <forkMode>pertest</forkMode> I am obliged to use version 2.2 because I use TestNG. Why the patch is not applied, in 2.3-SNAPSHOT ? Applied in this commit (see patch in
Revision: 479603 Modified : /maven/surefire/trunk/surefire-api/src/main/java/org/apache/maven/surefire/report/XMLReporter.java This got fixed at some point. Checked in an integration test in revision 597279.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||