Enunciate

Let maven-enunciate-plugin create the Java client jar as a separate Maven project

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major 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 :
    0

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Olle Hallin added a comment -

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).

Show
Olle Hallin added a comment - 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).
Hide
Permalink
Ryan Heaton added a comment -

See the following FAQ:

http://docs.codehaus.org/display/ENUNCIATE/Client-side+artifacts+and+Maven

Show
Ryan Heaton added a comment - See the following FAQ: http://docs.codehaus.org/display/ENUNCIATE/Client-side+artifacts+and+Maven

People

  • Assignee:
    Ryan Heaton
    Reporter:
    Olle Hallin
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: