You could declare a dependency to a in b's project.xml (even if you don't need the jar it produces). Or you could ude two maven:maven tags instead of one maven:reactor tag.
Aslak > -----Original Message----- > From: James CE Johnson [mailto:[EMAIL PROTECTED] > Sent: 24. mars 2003 17:39 > To: [EMAIL PROTECTED] > Subject: Reactor and dependencies... > > > Heya, > > I've got two sub-projects A & B. > > A creates a jarfile of deployable EJBs. I need to deploy those before I > can deploy the warfile created by B. > > [A has a JMS queue that B submits things into] > > In the parent directory of A & B I have a maven.xml that invokes > the reactor: > > <goal name="deploy-all" > description="Deploy each project's workspace"> > > <maven:reactor basedir="${basedir}" > includes="*/project.xml" > goals="master-deploy" > banner="Deploying project" > ignoreFailures="false" > /> > </goal> > > B doesn't have A's jarfile listed in its dependencies because it doesn't > need anything in that jarfile so the reactor won't necessarily invoke > master-deploy on A before B. Is there any way I can force A to be deployed > first? > > > --------------------------------------------------------------------- > 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]
