Skip to content
This repository has been archived by the owner on Sep 21, 2022. It is now read-only.

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

Open
glassfishrobot opened this issue Oct 18, 2013 · 4 comments
Open

Comments

@glassfishrobot
Copy link
Contributor

Adding source encoding to a POM:
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

Causes wsimport to fail:
[INFO] jaxws:wsimport args: [-keep, -s, 'C:<source>\trunk\target\generated-sources\wsimport', -d, 'C:<source>\trunk\target\classes', -verbose, -encoding, UTF-8, -extension, -Xnocompile, -target, 2.1, -b, 'C:<source>\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
Copy link
Contributor Author

Reported by shelly2k

@glassfishrobot
Copy link
Contributor Author

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
Copy link
Contributor Author

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

@glassfishrobot
Copy link
Contributor Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants