http://jira.codehaus.org/browse/MNG-743
that jira issue has a pretty good layout in my opinion...it has a sample jar that builds out everything into empty artifacts and can be a good way of getting going. On 9/30/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote: > > I ment to send this to the users list. Sorry for the double post! > > Cheers, > Thomas > > On 9/30/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I am wondering what the best way is to setup a project layout with M2 > and > > Eclipse for multiple modules. The documentation< > http://maven.apache.org/maven2/getting-started.html>recommends the > following: > > > > +- pom.xml > > +- my-app > > | +- pom.xml > > +- my-webapp > > | +- pom.xml > > > > > > The only way I can see this work with Eclipse is to add the entire > > structure to a single Eclipse project. However this is not something I'd > > want to do because I don't want to have a single Eclipse classpath that > is > > exposed to my-app and my-webapp. > > > > The only way around this, that I can currently see, is to do this: > > > > +- my-master > > | +- pom.xml > > +- my-app > > | +- pom.xml > > +- my-webapp > > | +- pom.xml > > > > In this scenario; my-master, my-app, and my-webapp are all seperate > > Eclipse projects. To make this work, I need to change the master POM's > > modules element to the following: > > > > <modules> > > <module>../my-app</module> > > <module>../my-webapp</module> > > </modules> > > > > Have I missed something or is this the recommended way? > > > > Thanks! > > > > Thomas > > > > -- jesse mcconnell
