maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Zeller (JIRA) <j...@codehaus.org>
Subject [jira] (SUREFIRE-1137) Problem with Umlauts in stdout
Date Tue, 27 Jan 2015 09:23:22 GMT

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

Jürgen Zeller commented on SUREFIRE-1137:
-----------------------------------------

Hallo Andreas,

here are my results:
bq. Oh and to be on the safe side: please also check with Surefire 2.18.1
No changes, Umlaut in stdout XML tag still in Cp1252 instead of UTF-8

bq.  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).
The default encoding on Windows is Cp1252, the default encoding on Linux is UTF-8
When i run the test without the fork argLine (and therefore use the default encoding), everything
is fine on Linux but that doesn't help my because the file encoding must be Cp1252.

bq.  Also, please check what happens if you run the tests with forkCount=0.
It works (obviously) because now the file encoding is UTF-8 as no seperate VM is started,
but i need dat encoding ;-)

bq.  Can you check what happens if you use UTF-8 as encoding? (don't forget to convert the
AppTest.java appropriately)
nothing changed

bq.  What happens if you add -Dfile.encoding=Cp1252 to your MAVEN_OPTS?
Now the stdout is no longer 4 Byte Cp1252 but broken UTF-8 rencoded stuff (like öäü�)
but also the message in the XML itself is broken.

Viele Grüße aus München,

Jürgen


> 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
>            Assignee: Andreas Gudian
>         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