search

javaee / metro-jaxws-commons

Metro has been contributed to Eclipse Foundation. This repository is for legacy review only. Please refer to the Eclipse EE4J Metro project for the very latest
https://eclipse-ee4j.github.io/metro-wsit/
Other
10 stars 9 forks source link

Specifying project.build.sourceEncoding causes wsimport to fail #117

Open glassfishrobot opened 10 years ago

glassfishrobot commented 10 years ago

Adding source encoding to a POM:

UTF-8 Causes wsimport to fail: [INFO] jaxws:wsimport args: [-keep, -s, 'C:\\trunk\target\generated-sources\wsimport', -d, 'C:\\trunk\target\classes', -verbose, -encoding, UTF-8, -extension, -Xnocompile, -target, 2.1, -b, 'C:\\trunk\src\main\resources\jaxb2Bindings.xjb', "file:/C://trunk/src/main/webapp/wsdl/.wsdl"] unrecognized parameter -encoding Pom build plugin section: org.jvnet.jax-ws-commons jaxws-maven-plugin 2.3.1-b03 wsimport $ {project.build.outputDirectory}/jaxb2Bindings.xjb ${project.build.outputDirectory} /wsdl true 2.1 true You will notice that I have also tried the -Xnocompile just in case that helped, but it didnt. If the sourceEncoding setting is removed from the POM the incorrect -encoding parameter is not generated and the tool executes ok. #### Environment maven 3.0.4, Win XP & RHEL6, Java 1.7.0_40, jaxws-maven-plugin 2.3 & 2.3.1-b03 #### Affected Versions [2.3]
glassfishrobot commented 10 years ago

Reported by shelly2k

glassfishrobot commented 10 years ago

shelly2k said: Sorry, further research. I have discovered in a child pom the following section added to the plugin section:

com.sun.xml.ws jaxws-tools 2.2.5

Removing this dependency fixed the issue.

glassfishrobot commented 10 years ago

@lukasj said: at least version 2.2.6 of jaxws-tools is needed for encoding parameter to work

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA JAX_WS_COMMONS-117