Hi,
On 5/31/06, Barrie Treloar <[EMAIL PROTECTED]> wrote:
> Now Maven is calling the assembly plugin in each module. It then fails
> because there is no
> package-all.xml in the module src tree (package-all.xml lives in the
> parent src).
>
> Is this the expected behaviour?
Probably, because your modules all specify this pom as the parent right?
So it gets inherited.
I've set <inherited>false</inherited> in the parent POM for the assembly plugin.
According to the POM descriptor this indicates "Whether any
configuration should be propagated to child POMs" so I would expect
this to not be used by any child modules.
Running help:effective-pom in a child module however shows the
assembly plugin to be configured here from the parent. Is this a bug
or is my understanding of the 'inherited' configuration option
incorrect?
You probably want to move the packaging stuff out into its own project
so that the parent pom does not have inherited values and local
values.
The only trouble with this is that I then have to specifically include
each module to be packaged. I would like to get this automagically
from the parent's module list. If this is not possible I'd appreciate
a definitive answer so I can move on to a different solution.
I guess my fundamental question is: Is it possible to create an
assembly of child module artifacts from the parent project?
If so, what specific assembly plugin configuration elements are
required in the parent POM?
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
