[ 
https://issues.apache.org/jira/browse/CXFXJC-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXFXJC-26.
-------------------------------
       Resolution: Fixed
         Assignee: Daniel Kulp
    Fix Version/s: 3.2.2

I added an encoding configuration for the plugin which will read the default 
from project.build.sourceEncoding.

You can work around this by adding extensionArgs to the xsdOption:

{noformat}
<extensionArgs>
   <arg>-encoding</arg>
  <arg>UTF-8</arg>
</extensionArgs>
{noformat}


> cxf-xjc-plugin generated source encoding problem
> ------------------------------------------------
>
>                 Key: CXFXJC-26
>                 URL: https://issues.apache.org/jira/browse/CXFXJC-26
>             Project: CXF XJC Utils
>          Issue Type: Bug
>          Components: Maven Plugin
>         Environment: Apache Maven 3.2.5 
> (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T18:29:23+01:00)
> Maven home: C:\devenv\apache-maven-3.2.5
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
>            Reporter: Bernd Eckenfels
>            Assignee: Daniel Kulp
>            Priority: Minor
>              Labels: i18n
>             Fix For: 3.2.2
>
>
> When using  cxf-xjc-plugin:3.1.0:xsdtojava on my german Windows 10 the 
> generated source code uses german language comments with the word "für" 
> (umlaut). The source seems to be in latin1 whereas the project is configured 
> to use UTF-8 source encoding. For this reason the following processing steps 
> (compiler warn and javadoc error) fail because of invalid UTF-8 sequences. It 
> should allow to define the encoding and default to the maven.source.encoding. 
> I also did not find a way to actually generate english comments 
> (MAVEN_OPTS=-Duser.language=en does help).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to