Hi - we have a classical jee setup with jar/war/ear and a ws-client
dep: ear <- war <- jar
the ws-client is part of the same multimodule as the others - same parent
and all.
The ws-client has:
<build>
<plugins>
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<phase>generate-sources</phase>
<goals>
<goal>unpack</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>${project.groupId}</groupId>
<artifactId>SomeModuleWAR</artifactId>
<type>war</type>
<version>${project.version}</version>
</artifactItem>
</artifactItems>
<includes>**/*.wsdl</includes>
</configuration>
</execution>
</executions>
</plugin>
inside it (to unpack wsdls and generate clients).
I fI do release:prepare -DdryRun=true on the whole multimodule it's OK.
It fails when doing release:prepare for real - because the SomeModuleWAR
is not available in local repo because the default prepare goals are:
clean verify :
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#preparationGoals
now - why does this fail? does the dependency plugin check for the
artifact before it'sr eally executed? because clean verify should not
trigger generate-sources - where the dep. is needed:
http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html
Anybody else hit this?
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
