> You could declare a dependency to a in b's project.xml (even if you > don't need the jar it produces).
A doesn't produce a jarfile so I'm not really sure what I would put in project.xml that wouldn't make it angry. A's purpose is only to deploy a jarfile (of EJBs) that someone else put into maven.repo.local. > Or you could ude two maven:maven tags > instead of one maven:reactor tag. I actually have a half-dozen sub-projects and B depends on some of those as well. Things might get weird if I start trying to resolve the dependencies manually. Maybe I should have B/maven.xml use the maven:maven tag to jump over to A's project and invoke its deploy goal... > > 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]
