[
https://issues.apache.org/jira/browse/CXF-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755403#action_12755403
]
Trygve Laugstøl commented on CXF-2275:
--------------------------------------
@Christian: Yes, I really think it is better. I actually hope you don't
implement a solution that's based around downloading stuff from a repository as
you're bypassing a very important part of Maven (dependency management).
You don't need to do anything special to use the reactor, it is a built-in
thing in Maven.
It works like this:
Project Api has a web service annotated interface and generates a WSDL that's
also attached to the build and put in the repository
Project Server has a dependency on the Api project's JAR (the one with the
normal Java interfaces)
Project Client has a dependency on the Api project's WSDL (just because it
feels like it)
Now, if I as a developer want to build this project from scratch, Maven has to
know which order to build them in. Maven does this by putting all of the
projects into a reactor and take a look at their dependencies. As Server and
Client both depend on API, it will make sure to build the API module first.
> Maven plugins: Support reading WSDLs from Maven repository
> ----------------------------------------------------------
>
> Key: CXF-2275
> URL: https://issues.apache.org/jira/browse/CXF-2275
> Project: CXF
> Issue Type: New Feature
> Components: Tooling
> Affects Versions: 2.2.2
> Reporter: Trygve Laugstøl
> Assignee: Christian Schneider
> Fix For: 2.3
>
>
> The Maven plugins should support reading WSDL files directly from a Maven
> repository to make it easier to consume WSDLs in a repository. Currently it
> is required to use the dependency plugin or similar to copy the WSDL from the
> repository to target/ to process it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
