Skip to main content

JAX-WS Maven 2 Plugin 1.12 released

Posted by ramapulavarthi on April 29, 2009 at 1:49 PM PDT

JAX-WS Maven2 plugin 1.12 is released which has some bug fixes related to configuring the wsimport/wsgen options and minor usability issue. JAX-WS maven plugin 1.12 depends on recently released JAX-WS RI 2.1.7. Along with other changes in JAX-WS RI 2.1.7, For maven users it has one important bug fix related to the dependency on the woodstox.

Just a recap on the previous 1.11 release, If you have n't noticed, In 1.11 wsimport goal default behavior is changed to not compile the generated sources. This was fixed as JAX-WS-COMMONS-25.

Fixes in 1.12 release are

  • JAX-WS-COMMONS-36: wsgen extension option is not working with the maven plugin.
  • JAX-WS-683: Confusing Warning "Nothing to do, no WSDL found!" with wsimport goal.

You can find more about the plugin usage at jax-ws commons project.
Do let us know if you see any issues with using the maven plugin.

Related Topics >>


<p>When using v1.12 of the jaxws-maven-plugin, I've noticed ...

When using v1.12 of the jaxws-maven-plugin, I've noticed that JAX-WS RI 2.1.7-b07 is being used. Comments in the generated classes: "This class was generated by the JAX-WS RI. JAX-WS RI 2.1.7-b01- Generated source version: 2.1". How could this be changed, such that JAX-WS RI 2.1.7 is being used.

PS: What is the latest released version of JAX-WS RI ?

Snippet from the pom.xml I'm using:


Bug report ?

I've got a strange error with 1.12 error: error reading C:\Documents and Settings\apa\.m2\repository\jade\framework\jade-libs-pom\2.0.27\jade-libs-pom-2.0.27.pom; error in opening zip file Why is the plugin trying to open my pom type dependency as if it was a zip ?

issue 53

I created a issue for this:

Seems pushing a artifact to Maven Central repo requires all its dependencies to be available at central repo. This requires all JAX-WS RI artifacts to be on Maven central. JAX-WS 2.1.X RI requires correct dependencies for jax-ws 2.1 api which has correct dependencies on 181-MR jar and others.There are some issues with jaxws-api 2.1 pom in Maven central. I have blogged about the situation earlier at

Maven repo

Still no updates on this front ?
Looks like it work if you put:
<id>Java dot Net</id>
<name>Repository for JAX-WS commons</name>
You don't have to manually download it from ?
Regards Bruno

Hi, This is a useful upgrade. Just one question: why don't you put this plugin immediately to central maven2 repository ( I noticed all JAX-WS Maven 2 Plugins, up to version 1.10 are there.