I see 2 ways to avoid this problem.
1.) I assume that war A includes a kind of 'common logic', right? If so, this
may also be
extracted into a separate module, thus you have no dependency to a war
anymore...
2.) You can use the exclude mechanism of the maven-war-plugin.
LieGrü,
strub
--- tadamski <[EMAIL PROTECTED]> schrieb:
>
> I'm working with maven 2 and using the war plugin. In my project I have a
> module that depends on another module. So if module B depends on module A,
> when I run the package goal, nodule A's war structure is overlayed on module
> B's war. Is there anyway to stop this from occurring? There are unnecessary
> directories and files being added, bloating the war.
Heute schon einen Blick in die Zukunft von E-Mails wagen?
www.yahoo.de/mail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
