[jira] Commented: (MSUREFIRE-172) Bug into xml report generation

["Milos Volauf (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MSUREFIRE-172?page=comments#action_84836 ] 
            
Milos Volauf commented on MSUREFIRE-172:
----------------------------------------

Hi.

I am also voting for this bug to be fixed.

Here is a hint for the fix:

in the module surefire-api, the class org.apache.maven.surefire.report.XMLReporter
should implement a method:

    public void testSetStarting(ReportEntry report) throws ReporterException {
    	super.testSetStarting(report);
    	
    	results.clear();
    }

(before each start, previous result should be cleared. AbstractTextReporter does the same.)

I tried it locally and it works.

Can someone provide a guess when this fix could appear in the released plugin (e.g. maven-surefire-plugin version 2.2.1 or something) ?

> Bug into xml report generation
> ------------------------------
>
>                 Key: MSUREFIRE-172
>                 URL: http://jira.codehaus.org/browse/MSUREFIRE-172
>             Project: Maven 2.x Surefire Plugin
>          Issue Type: Bug
>          Components: xml generation
>         Environment: release 2.0 of maven-surfire-plugin
> mvn 2.0.4
>            Reporter: Christophe Lallement
>         Attachments: nick.zip, TEST-deai.ft.archi.common.debug.ThreadWarningSystemTest.xml, ThreadWarningSystem.java, ThreadWarningSystemTest.java
>
>
> since 2-3 weeks i have wrong information into my junit test tun (mvn test for example)
> In fact, the *.txt are right, but the corresponding xml file have wrong entry. i means additionnal testcase are present ninto the testcase section.
> you can find exmple in attachement (ThreadWarningSystemTest for example). You can see that the error number are good (because read into the attribute of the first xml tag) but in several TestSuite, we have testcase form other testsuite.
> I don't know if this errors comes from maven dependancies update.
> What i am sure is: 
> 1/ a little bit of source modification into my project since this error appears.
> 2/ no new maven dependancies into my project
> 3/ i use only ibilio/maven2 as repository.
> This errors can'be shown on other projet and other not ...
> I have a workaround to solve this issue but with low performance:
>  I use the option "fork per test" and the reports is right.
> Maybe a way to be investigate can be the temporaly file created by the command line: 
> Forking command line: java -classpath 
> > C:\HOMEWARE\maven-2_local\org\apache\maven\surefire\surefire-api\2.0\surefire-api-2.0.jar;C:\HOMEWARE\maven-2_local\o
> > rg\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;C:\HOMEWARE\maven-2_local\org\apache\maven\surefire\surefire-booter\2.0\surefire-booter-2.0.jar or
> > g.apache.maven.surefire.booter.SurefireBooter C:\temp\surefire40840tmp C:\temp\surefire40841tmp
> Any Idea ?
> Thx
> Christophe

-- 
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