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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
