jaxws-maven-plugin maven project dependencies are old (2.0.4, while 3.0 is out)

[glassfishrobot]

The pom.xml depends on "old" maven modules. In maven 3.0 the code has been changed a lot. The jaxws-maven-plugin uses the maven plugin to construct the classpath for wsgen.

Proposal move to the latest maven project versions, e.g. use:

com.sun.xml.ws jaxws-tools 2.1.7 org.apache.maven maven-project 3.0-alpha-2 org.apache.maven maven-plugin-api 3.0.2

This also solves the following problem:

• module with jaxws-maven-plugin using wsgen builds correctly when build standalone
• the same module as part of a large module hierarchy fails to build. The wsgen classpath contains jars on the classpath of unrelated modules. The resolving of these modules is caused by the code in maven-project.

Tested: using above dependencies the build problem is solved and wsgen is executed with the correct classpath.

Affected Versions

[current]

[glassfishrobot]

Reported by escay

[glassfishrobot]

jroyals said: Probably worth underlining that this plugin in incompatible with Maven 3, for the above reason. Here is the error message...

---

[ERROR] Failed to execute goal org.codehaus.mojo:jaxws-maven-plugin:1.12:wsimport (default) on project elmi-client: Execution default of goal org.codehaus.mojo:jaxws-maven-plugin:1.12:wsimport failed: Plugin org.codehaus.mojo:jaxws-maven-plugin:1.12 or one of its dependencies could not be resolved: Failed to collect dependencies for org.codehaus.mojo:jaxws-maven-plugin:jar:1.12 (): Failed to read artifact descriptor for com.sun.xml.ws:jaxws-tools:jar:2.1.7: Could not transfer artifact com.sun.xml.ws:jaxws-tools:pom:2.1.7 from maven1-repository.java.net (http://download.java.net/maven/1/)::) No connector available to access repository maven1-repository.java.net (http://download.java.net/maven/1/) of type legacy using the available factories WagonRepositoryConnectorFactory -> [Help 1]

[glassfishrobot]

@lukasj said: this needs to be addressed

[glassfishrobot]

@lukasj said: Some project dependencies are going to be updated within #74 but since JAX-WS 2.1.x and its dependencies are still available in Maven 1 legacy repo only, it is not possible to use it from Maven3 - this is to be addressed within #52, hence marking as a dup of it

[glassfishrobot]

@lukasj said: to re-close with proper fix version

[glassfishrobot]

@lukasj said: closing old and already fixed issues

[glassfishrobot]

Issue-Links: is related to JAX_WS_COMMONS-52

[glassfishrobot]

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

[glassfishrobot]

Marked as duplicate on Wednesday, October 12th 2011, 7:03:53 am