You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2018/05/06 11:23:00 UTC
[jira] [Updated] (SUREFIRE-1495) Encoding of TXT report file should
be configured by ${project.reporting.outputEncoding} and MOJO parameter
encoding
[ https://issues.apache.org/jira/browse/SUREFIRE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tibor Digana updated SUREFIRE-1495:
-----------------------------------
Fix Version/s: (was: 3.0.0-M1)
2.22.0
> 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: 2.22.0
>
>
> 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)