[
https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362274#comment-362274
]
Michael Osipov commented on SUREFIRE-1137:
------------------------------------------
[~zet],
there is no bug (yet). First, {{javac}} reads your Java source with ISO-8859-15
and the std out is correct. There is no connection to {{file.encoding}}.
Second, you test sample does not contain any resources but Java files only. I
see no problem. Third, if your test resources are not in the encoding as
{{file.encoding}} and surefire did ignore {{project.build.sourceEncoding}} then
this is a bug but you haven't provided a valid sample project Even though, I
would be confused because surefire does not read any test resources but your
testcases do.
> 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)
