Thank you that's been really helpful. I've copied this to the Maven Users list so its there for others to read.
On 24/10/05, Jose Gonzalez Gomez <[EMAIL PROTECTED]> wrote: > See inline... > > 2005/10/24, Pete <[EMAIL PROTECTED]>: > > Thank you Jose, that's a lot clearer now. Just a couple more questions > > if I may :- > > > > 1) So in your pseudo root project e.g. > > > > +project > > pom.xml > > > > do you reference the child modules like this ? > > > > <modules> > > <module>../modules/domain</module> > > <module>../modules/web</module> > > <module>../applications/j2ee</module> > > </modules> > > > > You're right > > > 2) How do developers check out the project from say CVS, do you put > > your root e.g yourproject in SCM ?. > > > > yourproject > > +project > > +modules > > > > Then let developers use the Eclipse import from the yourproject root ? > > > > Again you're right, but note that you shouldn't do that first check > out from within Eclipse. If you do so, Eclipse will create a project > in the root folder, something you want to avoid (well, you just may > delete it after doing the first checkout). I usually follow these > steps: > 1. Check out project from repository, using a command line tool, or > maven scm support. > 2. Change to yourproject/project directory > 3. Run mvn eclipse:eclipse. That will generate eclipse projects for > all your modules, including direct project dependencies among between > modules in the same project > 4. Import all the generated projects > 5. Create manually a project for yourproject/project so you're able to > edit your root pom in case you need it. > > HTH, best regards > Jose > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
