[SUREFIRE-1052] Use "project.build.sourceEncoding"-Property by default for forked jvm

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.10, 2.16
• Component/s: classloading, Maven Surefire Plugin, process forking
• Assignee: Unassigned
• Reporter: Dieter König
• Created: 09/Jan/14 07:26
• Updated: 11/Dec/14 04:55
• Resolved: 11/Dec/14 04:55

Description

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.