[
https://issues.apache.org/jira/browse/SUREFIRE-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028003#comment-16028003
]
Hudson commented on SUREFIRE-1375:
----------------------------------
SUCCESS: Integrated in Jenkins build maven-surefire #1710 (See
[https://builds.apache.org/job/maven-surefire/1710/])
[SUREFIRE-1375] Fixing build on Windows cmd.exe (tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=63657b6e754c378ce26f8cc75781f29671187b17])
* (edit) maven-failsafe-plugin/pom.xml
> Fixing build on Windows cmd.exe
> -------------------------------
>
> Key: SUREFIRE-1375
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1375
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Failsafe Plugin
> Affects Versions: 2.20
> Reporter: Guillaume Boué
> Assignee: Tibor Digana
> Fix For: 2.20.1
>
>
> The Failsafe Plugin uses {{cxf-xjc-plugin}}, and the XJC tool, to generate
> files from an XSD. Currently, those files are written with the platform
> encoding, that can be different from the project source encoding.
> In a Windows environment, on the command prompt, we can have {{chcp}} telling
> us it's using code page 850. In turn, this creates an error while compiling
> the generated sources because they contain unmappable characters for UTF-8 as
> expected by the compiler.
> {noformat}
> [INFO] --- maven-compiler-plugin:3.6.1:compile (compile-generated) @
> maven-failsafe-plugin ---
> [INFO] Changes detected - recompiling the module!
> ...
> [ERROR]
> C:\...\maven-surefire\maven-failsafe-plugin\target\generated-sources\jaxb\org\apache\maven\plugin\failsafe\xmlsummary\ObjectFactory.java:[2,16]
> error: unmappable character for encoding UTF-8
> {noformat}
> The encoding that should be used by XJC is specified through the
> {{-encoding}} option and should be set to the project source encoding.
> [Pull request #151|https://github.com/apache/maven-surefire/pull/151].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
