As for your second paragraph with modE, you would simply create /project/modE and add it as a dependency in modB.
Then you could access the settings in modE for use in modB. It would be similar to modA in that it would have no dependencies itself. I think your best advice is to simply "jump in with both feet" and figure things out as you get to them. ;-) Wayne On 4/27/06, Wayne Fay <[EMAIL PROTECTED]> 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 > > On 4/27/06, Clifton Craig <[EMAIL PROTECTED]> wrote: > > Hello all, > > > > I'm relatively new to Maven2 and I'd like somebody to explain the > > multi-module > > support in a little more detail. We have some projects that we're managing > > with M2. I'm not sure that I want to use multi-module support because it > > seems a little restrictive as explained on the site. However, I'm afraid > > that > > I may need some of the features from mult-module support. Let me clarify. > > Take the following example: Projects A, B, C, and D. B, C, and D all depend > > on A. C and D depend on B. The one problem (due to my lack of understanding) > > I have is that for multi-module support to work, as I understand it, I would > > need to reflect the module dependencies in the directory structure of the > > modules. This means a module folder would need to sit atop of its dependency > > module folders. In my example there is no clean way (short of using > > replicating modules or icky non-x-platform symbolic links) to acheive the > > relationship in the directory structure. So it makes better sense to layout > > all modules as peers including parent modules and folders with parent pom > > files. I'm not sure if this is supported or I'm not understanding the > > workings correctly. > > > > The other problem I have is that if my prior explanation is not accurate how > > would we make the association evident in child modules to their parents? In > > other words, assume I have all modules A-D laid out as peers on the > > filesystem. Also assume that there is a global module, E, that contains > > settings that are inherited by the others A-D. (E is also a peer.) If I'm > > working in the folder for B and decide to run "mvn test" or "mvn deploy", > > how > > then does it know to look into the peer folder for E for inherited settings? > > It seems to me that either some sort of reference need to be made to the > > location of E or E would need to be installed first before testing or > > deploying B. I'm sure I have some things misunderstood but could somebody > > clear things up for me? > > > > --------------------------------------------------- > > Clifton C. Craig, Software Engineer > > Intelligent Computer Systems - A Division of GBG > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
