On Mon, Aug 25, 2008 at 4:15 PM, Trevor Harmon <[EMAIL PROTECTED]> wrote:
> I've been reading that modules are the solution to this problem. There's a > write-up about them here: > http://docs.codehaus.org/display/MAVENUSER/Multi-modules+projects > However, the solution in the write-up doesn't seem like it would work, at > least not in my situation. It says I have to specify libC's parent module, > but which parent do I choose? As you can see above, it has two parents: appA > and appB. How can I reconcile this? Thanks, In your example, appA and appB are not parents of libC... they simply have a dependency on it. If you establish a parent pom, and list all five of your projects as <modules>, Maven will figure out what order to build them in, and compile the changed sources. (It might not be quite as efficient as Ant, for example I think if you run 'mvn install' it will still package up and install the jar, even if nothing needed to be compiled. YMMV.) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
