Right, if you use <id>, then the groupId and artifactId are the value of <id>...
If you take the approach I took, using <artifactId> in each of the sub-projects, then your first example would work. T -----Original Message----- From: Louis Burroughs [mailto:[EMAIL PROTECTED] Sent: Friday, November 12, 2004 11:23 AM To: Maven Users List Subject: RE: Problem with Reactor build order What I have found so far is that when I went from trying to group all of my artifacts under one group Id to their own group Id then reactor picked up the build order correctly, but when the ear was building now it couldn't find the war files in the repository. I tried messing around with the id's in the poms, but that caused the code in my war file not to compile. Before: <groupId>${pom.groupId}</groupId> <artifactId>war1</artifactId> <version>${pom.currentVersion}</version> After: <groupId>war1</groupId> <artifactId>war1</artifactId> <version>SNAPSHOT</version> "Poppe, Troy" <[EMAIL PROTECTED]> 11/12/2004 10:25 AM Please respond to "Maven Users List" To: "'Maven Users List'" <[EMAIL PROTECTED]> cc: bcc: Subject: RE: Problem with Reactor build order I have actually put <artifactId> tags in my sub-projects rather than <id>... This seems to work out much better than <id> for me. T -----Original Message----- From: Louis Burroughs [mailto:[EMAIL PROTECTED] Sent: Friday, November 12, 2004 10:01 AM To: Maven Users List Subject: Re: Problem with Reactor build order The only potential issue I see in my project.xml is that my top level id is the same as my ear name. Top <id>IPM</id> <name>Initiative Performance Measurement</name> <currentVersion>2.2-Release</currentVersion> Ear <extend>${basedir}/../project.xml</extend> <id>Project</id> <name>IPM</name> War1 <extend>${basedir}/../project.xml</extend> <id>ProjectTest</id> <name>Connectivity Test Project</name> War2 <extend>${basedir}/../project.xml</extend> <id>ProjectWeb</id> <name>IPM web application</name> Louis M. Burroughs III, OCTO Jeffrey Mutonho <[EMAIL PROTECTED]> 11/12/2004 09:47 AM Please respond to "Maven Users List" To: Maven Users List <[EMAIL PROTECTED]> cc: bcc: Subject: Re: Problem with Reactor build order Hmmm...when I had a similar problem of a messed build order , it was because a "copy and paste" error in one of my project.xml files .I had the same <id>"blah_blah"</id> <name>blah blah</name> in the project.xml files for two different projects.I had copied and pasted from one project.xml file to the other and forgot to change values for the <id> and <name> fields jeff mutonho On Fri, 12 Nov 2004 09:39:23 -0500, Louis Burroughs <[EMAIL PROTECTED]> wrote: > I am having trouble with Reactor changing the build order in my > project when the dependencies have not changed. At one point I manged > to get my two war files built and installed in the local repository, > then the ear file was built. After I added more goals, my build order > went to fifo (first in first out). The adding of the other goals may > be totally incidental, but something other than dependency is > effecting Reactor's processing order and I can't find it can someone > help? > > My Project Structure: > > -top > -ear > -war1 > -war2 > > Top Level maven.xml: > > <?xml version="1.0"?> > <project default="ipm:build-all" xmlns:j="jelly:core" xmlns:maven="jelly:maven"> > <goal name="ipm:build-all"> > <maven:reactor basedir="${basedir}" includes="*/project.xml" goals="ipm-dist" banner="Building" ignoreFailures="false"/> > </goal> > <preGoal name="ipm:build-all"> > > Checkout from CVS.......... > > </preGoal> > <postGoal name="ipm:build-all"> > > Cleanup............... > > </postGoal> > </project> > > ear project maven.xml: > > <project default="ipm-dist" xmlns:j="jelly:core" xmlns:maven="jelly:maven"> > <goal name="ipm-dist"> > <attainGoal name="ear:install" /> > </goal> > <goal name="goal2"> > Do something else...... > </goal> > </project> > > war projects maven.xml (There are 2 but they both look the same): > > <project default="ipm-dist" xmlns:m="jelly:maven"> > <goal name="ipm-dist"> > <attainGoal name="war:install"/> > </goal> > </project> > > ear project project.xml dependencies: > > <dependencies> > Other dependencies > <dependency> > <groupId>${pom.groupId}</groupId> > <artifactId>war1</artifactId> > <version>${pom.currentVersion}</version> > <type>war</type> > <properties> > <ear.bundle>true</ear.bundle> > <ear.appxml.ear.context-root>war1</ear.appxml.ear.context-root> > </properties> > </dependency> > <dependency> > <groupId>${pom.groupId}</groupId> > <artifactId>war2</artifactId> > <version>${pom.currentVersion}</version> > <type>war</type> > <properties> > <ear.bundle>true</ear.bundle> > <ear.appxml.ear.context-root>war2</ear.appxml.ear.context-root> > </properties> > </dependency> > </dependencies> > > Reactor output: > > Starting the reactor... > Our processing order: > ear > war1 > war2 > +---------------------------------------- > | Building IPM > | Memory: 9M/13M > +---------------------------------------- > > Louis M. Burroughs III, OCTO > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
