Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Not A Bug
-
Affects Version/s: 1.21.1
-
Fix Version/s: 1.21.1
-
Component/s: None
-
Labels:None
-
Environment:Maven
-
Number of attachments :
Description
As it is today, the Enunciate Maven plugin can generate a client jar for the JAX-WS client.
It is generated with the Maven classifier "client".
Unfortunatly, this client jar is quite useless, since it shares the same pom as the implementation.
A Maven-built user of the JAX-WS endpoint cannot depend on this artifact, since it will bring in the entire server implementation transitively.
So instead I propose that Enunciate generates a completely separate artifact for the client jar, with a generated pom.xml that declares the minimal set of dependencies needed to access the service.
I'd like to rephrase the name of the issue:
"Let maven-enunciate-plugin create the Java client jar as a standalone Maven artifact"
The key thing is that it should have a separate artifactId and pom.xml from the main artifact (the war).