The solution outlined below is the recommended way to handle this.
Copy/unpack was meant to handle external artifacts.
--Brian (mobile)
On Dec 18, 2008, at 4:28 PM, Jamie Whitehouse > wrote:
I've run into a similar situation and I'll explain how I resolved this
problem. There are two way'
I've run into a similar situation and I'll explain how I resolved this
problem. There are two way's that I've solved this, both of which are
used to inform the reactor of the inter-module dependency:
1) Simply add SomeModuleWAR to your dependency list. This is generally
a good idea to help the re
> 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 depend
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:
maven-dependency-plugin
generate-sources
