Thanx Wayne, I think I'm learning a bit on my own too. I didn't realize that: 1. I could point the pom's parent to a relative path location. 2. I could install a pom on its own.
I started with option one but I think I'll continue with option 2. Though I know I could use both I'm not too comfortable with relative paths as it requires a fixed directory structure which I find potentially limiting. --------------------------------------------------- Clifton C. Craig, Software Engineer Intelligent Computer Systems - A Division of GBG [EMAIL PROTECTED] [EMAIL PROTECTED] On Thursday 27 April 2006 2:53 pm, Wayne Fay wrote: > I think you're just a little confused... ;-) > > Set it up as follows: > /home/maven/project > +pom.xml with <modules>modA, modB, modC, modD > /home/maven/project/modA > /home/maven/project/modB > +pom.xml with <dependency> modA > /home/maven/project/modC > +pom.xml with <dependency> modA, modB > /home/maven/project/modD > +pom.xml with <dependency> modA, modB > > Then run Maven2 from the parent directory. It will see all the modules > and poms, figure out (automatically) the order the modules need to be > built (using declared dependencies), and proceed with the build. > > Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
