FYI: I do it, but with an older Maven (yet it makes no difference). I have some "basic" WAR projects and specific derivatives of those. Using maven.xml from the derivate project I build the specific WAR dir (which contains only specific things) and after that I unpack the "basic" war with overwrite="false". Thus all needed basic components are "filled in" and I can override specific files by specifying them in the derivate project. There is a little headache caused by the "one-artifact-per-project" philosophy of older Maven, but I'm able to live with that.
I agree, not nice but handy (so far). Florin ----- Original Message ----- From: "solo turn" <[EMAIL PROTECTED]> To: "Maven Developers List" <[email protected]> Sent: Wednesday, August 17, 2005 12:31 PM Subject: [m2]: include war in war > hi, > > would it make sense to allow including a war into a war? so you could > take a standard war without touching it, and add specific things to > it, jars, tld, html, class. or would this be ugly? how would you do > that then? > > -solo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
