[ 
https://issues.apache.org/jira/browse/SUREFIRE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394460#comment-16394460
 ] 

ASF GitHub Bot commented on SUREFIRE-1495:
------------------------------------------

Github user eolivelli commented on a diff in the pull request:

    https://github.com/apache/maven-surefire/pull/176#discussion_r173648023
  
    --- Diff: 
surefire-its/src/test/java/org/apache/maven/surefire/its/fixture/HelperAssertions.java
 ---
    @@ -171,4 +172,9 @@ public static void assumeJavaVersion( double 
expectedVersion )
             assumeTrue( "java.specification.version: " + thisVersion,
                     Double.valueOf( thisVersion ) >= expectedVersion );
         }
    +
    +    public static String toUTF8( String unicode )
    --- End diff --
    
    maybe the name is not explaining the purpose of the function


> Encoding of TXT report file should be configured by 
> ${project.reporting.outputEncoding} and MOJO parameter encoding
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1495
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1495
>             Project: Maven Surefire
>          Issue Type: New Feature
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 3.0.0-M1
>
>
> According to the release vote [1] the integration test {{UnicodeTestNamesIT}} 
> fails due to Japanese encoding.
> The entire problem is with using only system file encoding in Surefire TXT 
> report files in {{target/surefire-reports}}, similar with Failsafe.
> [1]: [VOTE] Release Apache Maven Surefire Plugin version 2.21.0
> https://lists.apache.org/thread.html/eddec1bf40f900f07be67be9e79e686654fd6ec44c672a4ae58d4650@%3Cdev.maven.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to