With the help of Darren we solved the above problem quite elegantly:
To the generate-sources phase of the web service client we could bind the
following executions:
- a dependency-plugin call to copy to the target directory the war file
produced by the web service project
- jetty:start goal to sta
Do you have a sample for doing that? It's your solution generic?
I have a web services client application where I generate the artifact
sources during the generate-sources phase. In order to import the latest
version of the wsdl I try to kick-up a jetty server with the war produced by
another modu
Hi,
I was able to integrate in the WS client the jetty plugin in war mode and
setting explicitly the path to the other module's war package but now the
problem the build phase.
Could not convince jetty to start in the generate-sources phase...
Regards,
Jozsef
ZsJoska wrote:
>
>
9 at 8:52 AM, ZsJoska wrote:
>> How could I make the wsimport goal from myProject-wsclient to depend from
>> the jetty:run goal in the myProject-ws module.
>
> Why not create a POM that references these two projects a sub-modules.
>
> You can initiate the goal
Grant Rettke wrote:
>
> On Mon, Apr 27, 2009 at 1:48 PM, ZsJoska wrote:
>> Thanks for your answer but is that possible to attach to the
>> code-generation
>> (i think is more suitable) phase the jetty:run goal from/for another
>&g
Hi,
Thanks for your answer but is that possible to attach to the code-generation
(i think is more suitable) phase the jetty:run goal from/for another
pom.xml?
Grant Rettke wrote:
>
>> How could I do this automatically?
>
> Would attaching the jetty:run goal to the pre-test phase solve your
>
