[ 
https://jira.codehaus.org/browse/SUREFIRE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Rosenvold closed SUREFIRE-1006.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.16

Fixed in 54c46be0af7ce161f92f156df44569129ea9417c
                
> Junit report xml invalid utf8-caracters
> ---------------------------------------
>
>                 Key: SUREFIRE-1006
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-1006
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: xml generation
>    Affects Versions: 2.15
>         Environment: windows 7 64-bit, windows 2003 Server 32-bit. 
>            Reporter: Süleyman Vurucu
>            Assignee: Kristian Rosenvold
>            Priority: Critical
>             Fix For: 2.16
>
>
> trHi,
> I update surefire from 2.14 to 2.15 and my jenkins builds failed. After 
> looking why the builds are failed I see that Jenkins can't parse the JUnit 
> Results. I can't open this xml files in eclipse 4.3 as well. 
> After I compare the results from 2.14 and 2.15 I see the the sysout areas in 
> the TEST-*.xml in 2.14 are surrounded with <![CDATA sections and in 2.15 not. 
> And that's the problem. My testresults, which are logged, contains a lot of 
> ascii controll characters. 
> run this test with 2.14 and 2.15 and try it open in junit view of eclipse. 
> You'll se the dirrence ;-)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to