Thanks to all for your input. I was able to get the multiple project build working. One key element I was missing was the <parent> tag in my child project poms. one thing to note here is that when you add the <parent> nodes to the pom you need to run a "mvn install" on the parent project. Otherwise, I was having problems getting the child projects to build separately, because it was looking for the parent in the repository. I am not sure if I stated that clearly correct as I am still slightly confused, but I was able to get the builds working doing that.
The using eclipse link also helped me understand how to structure my project for use within eclipse and still fitting the maven structure needed. Check this link out for more information on that: http://maven.apache.org/guides/mini/guide-ide-eclipse.html Thanks again to all for their input. TJ On 3/25/06, Steven Coco <[EMAIL PROTECTED]> wrote: > > Hi. > > I have done multi-module POMs without any problem (Maven 2). > > The main POM excerpt you posted looks to be fine. In the child POMs, be > sure they refer to the parent: > > <parent> > <groupId>...</groupId> > <artifactId>...</artifactId> > <version>...</version> > </parent> > > And be sure any dependency between one module and another is properly > declared. > > Then if you are sure of the above, I would not know further. I have > done projects that all bundle into individual jars. There may be > another issue if one module is being jar'd and then that needs to be > assembled into the war. In theory, that all should work, but I don't > actually have a specific example POM to show you. > > Good luck. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
