Thanks, Greg. That's probably what I'll do. I didn't want other subprojects like EarSub to inherit a bunch of dependencies it doesn't care about, but maybe it's not a big deal.
On Thu, 18 Dec 2003, at 21:18:42 [GMT +0100] Gregory Joseph wrote: > Jeff, > How about having your sub* project.xml's extend a main one which would state > these dependencies? > (<project><extend>../project.xml</extend>...</project>) > greg > -----Original Message----- > From: Jefferson K. French [mailto:[EMAIL PROTECTED] > Sent: jeudi 18 décembre 2003 21:05 > To: Maven > Subject: Shared dependencies for jar and war > I'm in the process of migrating a J2EE Ant project to Maven. I'm using > multiproject and setting up three subprojects, one each for the > JarSub, WarSub, and EarSub. Many of the third-party jars used to build > JarSub are also needed at runtime in the war. Is there a better way to > reference those dependencies than duplicating most of them in WarSub's > project.xml file just to add the <war.bundle> property? Should the > <war.bundle> be in JarSub's project.xml? > I've been looking at the WebShop and Foobar-Travels examples, but I'm > missing something. > Jeff -- mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
