[
https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362272#comment-362272
]
Jürgen Zeller commented on SUREFIRE-1137:
-----------------------------------------
@Tibor: Yes, we have a bug in surefire.
@Michael: removing the
<argLine>-Dfile.encoding=${project.build.sourceEncoding}</argLine> is obviously
fixing the encoding issues but not the problem:
I need that encoding for running the tests, because the test file data is in
Cp1252, not in UTF-8
But when i change file.encoding, it also changes the encoding for stdout/stdin
in the forked JVM, and so the problems starts.
> 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)
