You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by deckrider <de...@gmail.com> on 2008/02/14 00:44:01 UTC
java -> java2wsdl -> wsdl2java
I have a multi-module project that begins with java, needs to generate
a wsdl, and then from that wsdl needs to generate more java.
The plugin I'm using for this is the axistools-maven-plugin.
Unfortunately this approach does not play well with the release
plugin. It works fine until it comes time for a release.
The problem appears to be that I need to have the jar created from the
original java in the _plugin_ dependencies, and that somehow causes
the following error during release:deploy that the jar (in a the first
sibling module) has not yet been uploaded to our archiva instance.
Anyone know how I can work around this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: java -> java2wsdl -> wsdl2java
Posted by deckrider <de...@gmail.com>.
My apologies, I was looking at the wrong build output. This does
appear to work around my problem.
However, I can't help but wonder if it is a bug that this must be
done, but perhaps I just don't understand yet.
Anyway, thanks much for the help!
On Feb 13, 2008 5:50 PM, deckrider <de...@gmail.com> wrote:
> This doesn't seem to have any effect in my case.
>
>
> On Feb 13, 2008 4:57 PM, Heck, Joe <Jo...@disney.com> wrote:
> > We've had a similar problem with some of our multimodule projects. We
> > found adding this additional configuration for the release plugin helped
> > resolve the issue:
> >
> > <plugin>
> > <artifactId>maven-release-plugin</artifactId>
> > <configuration>
> > <preparationGoals>install</preparationGoals>
> > </configuration>
> > </plugin>
> >
> > -joe
> >
> > Joseph Heck
> > Walt Disney Internet Group
> >
> >
> > -----Original Message-----
> > From: users-return-82581-Joe.Heck=dig.com@maven.apache.org
> > [mailto:users-return-82581-Joe.Heck=dig.com@maven.apache.org] On Behalf
> > Of deckrider
> > Sent: Wednesday, February 13, 2008 3:44 PM
> > To: Maven Users List
> > Subject: java -> java2wsdl -> wsdl2java
> >
> > I have a multi-module project that begins with java, needs to generate
> > a wsdl, and then from that wsdl needs to generate more java.
> >
> > The plugin I'm using for this is the axistools-maven-plugin.
> >
> > Unfortunately this approach does not play well with the release
> > plugin. It works fine until it comes time for a release.
> >
> > The problem appears to be that I need to have the jar created from the
> > original java in the _plugin_ dependencies, and that somehow causes
> > the following error during release:deploy that the jar (in a the first
> > sibling module) has not yet been uploaded to our archiva instance.
> >
> > Anyone know how I can work around this?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
>
> --
> ASCII ribbon campaign:
> () against HTML email
> /\ against Microsoft attachments
> Information: http://www.expita.com/nomime.html
>
--
ASCII ribbon campaign:
() against HTML email
/\ against Microsoft attachments
Information: http://www.expita.com/nomime.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: java -> java2wsdl -> wsdl2java
Posted by deckrider <de...@gmail.com>.
This doesn't seem to have any effect in my case.
On Feb 13, 2008 4:57 PM, Heck, Joe <Jo...@disney.com> wrote:
> We've had a similar problem with some of our multimodule projects. We
> found adding this additional configuration for the release plugin helped
> resolve the issue:
>
> <plugin>
> <artifactId>maven-release-plugin</artifactId>
> <configuration>
> <preparationGoals>install</preparationGoals>
> </configuration>
> </plugin>
>
> -joe
>
> Joseph Heck
> Walt Disney Internet Group
>
>
> -----Original Message-----
> From: users-return-82581-Joe.Heck=dig.com@maven.apache.org
> [mailto:users-return-82581-Joe.Heck=dig.com@maven.apache.org] On Behalf
> Of deckrider
> Sent: Wednesday, February 13, 2008 3:44 PM
> To: Maven Users List
> Subject: java -> java2wsdl -> wsdl2java
>
> I have a multi-module project that begins with java, needs to generate
> a wsdl, and then from that wsdl needs to generate more java.
>
> The plugin I'm using for this is the axistools-maven-plugin.
>
> Unfortunately this approach does not play well with the release
> plugin. It works fine until it comes time for a release.
>
> The problem appears to be that I need to have the jar created from the
> original java in the _plugin_ dependencies, and that somehow causes
> the following error during release:deploy that the jar (in a the first
> sibling module) has not yet been uploaded to our archiva instance.
>
> Anyone know how I can work around this?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
ASCII ribbon campaign:
() against HTML email
/\ against Microsoft attachments
Information: http://www.expita.com/nomime.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: java -> java2wsdl -> wsdl2java
Posted by "Heck, Joe" <Jo...@disney.com>.
We've had a similar problem with some of our multimodule projects. We
found adding this additional configuration for the release plugin helped
resolve the issue:
<plugin>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<preparationGoals>install</preparationGoals>
</configuration>
</plugin>
-joe
Joseph Heck
Walt Disney Internet Group
-----Original Message-----
From: users-return-82581-Joe.Heck=dig.com@maven.apache.org
[mailto:users-return-82581-Joe.Heck=dig.com@maven.apache.org] On Behalf
Of deckrider
Sent: Wednesday, February 13, 2008 3:44 PM
To: Maven Users List
Subject: java -> java2wsdl -> wsdl2java
I have a multi-module project that begins with java, needs to generate
a wsdl, and then from that wsdl needs to generate more java.
The plugin I'm using for this is the axistools-maven-plugin.
Unfortunately this approach does not play well with the release
plugin. It works fine until it comes time for a release.
The problem appears to be that I need to have the jar created from the
original java in the _plugin_ dependencies, and that somehow causes
the following error during release:deploy that the jar (in a the first
sibling module) has not yet been uploaded to our archiva instance.
Anyone know how I can work around this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org