Dieter König created SUREFIRE-1052:
--------------------------------------
Summary: Use "project.build.sourceEncoding"-Property by default
for forked jvm
Key: SUREFIRE-1052
URL: https://jira.codehaus.org/browse/SUREFIRE-1052
Project: Maven Surefire
Issue Type: Bug
Components: classloading, Maven Surefire Plugin, process forking
Affects Versions: 2.16, 2.10
Reporter: Dieter König
Attachments: pom.xml, SurefireEncodingTestCase.java
maven-surefire-plugin is ignoring "project.build.sourceEncoding"-property when
forking jvm for testcase execution.
The attached testcase fails with surefire for a project configured as UTF-8 but
is successful when executed in eclipse.
Known Workaround:
Configure surefire in the following way
<configuration><argLine>-Dfile.encoding=${project.build.sourceEncoding}</argLine></configuration>
P.S.: Unfortunately the oracle jvm itself is also unsafe. Executing the
testcase with java.exe (without file.encoding-argument) gives AssertionError,
executing with javaw.exe (without file.encoding-argument) is successful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
