Sounds like you want to unpack the EAR, add the WAR and repack it again... that would be a 2nd EAR module that depends on the first EAR and the WAR... might need some massaging, or perhaps a m-d-p:unpack-dependencies
On 18 October 2011 16:59, Brian Topping <topp...@codehaus.org> wrote: > How would you solve this problem without Maven? What kind of EAR could load > a WAR it doesn't know about? > > I don't doubt that this is possible with some magic, but that magic is > separate from Maven. > > Once you have the magic well-defined, Maven can help you build it and package > it. > > Brian > > On Oct 18, 2011, at 11:50 AM, Manos Batsis wrote: > >> >> Hello, >> >> I've got an EAR application for which I'm building a specific extension as >> an additional WAR. My question is, what is the best way to do this without >> the original EAR's POM knowing anything about the extra WAR? Any examples >> would be appreciated. >> >> >> Many thanks, >> >> Manos >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
