maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Gudian (JIRA)" <j...@codehaus.org>
Subject [jira] (SUREFIRE-1137) Problem with Umlauts in stdout
Date Mon, 26 Jan 2015 19:22:18 GMT

    [ https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361833#comment-361833
] 

Andreas Gudian commented on SUREFIRE-1137:
------------------------------------------

File-Encoding and Timezones are the two things that will keep all of us busy until the universe
collapses.

Jürgen, as I have no Linux system at hand right now, could you please:
* check if there is a difference in the system default encoding on both of your systems? (I
see that you try to switch it for the fork, but still). 
* Also, please check what happens if you run the tests with forkCount=0.
* What happens if you add -Dfile.encoding=Cp1252 to your MAVEN_OPTS?
* Can you check what happens if you use UTF-8 as encoding? (don't forget to convert the AppTest.java
appropriately)

Thanks!

> Problem with Umlauts in stdout
> ------------------------------
>
>                 Key: SUREFIRE-1137
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-1137
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.18
>         Environment: Linux
>            Reporter: Jürgen Zeller
>         Attachments: surefire-test.zip
>
>
> When using Cp1252 as file encoding, the generated Surefire stdout report contains invalid
characters when run on Linux. When running the same test on Windows, everything is fine.
> A simular Problem was reported in SUREFIRE-998



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message