Hello,
You can filter the subprojects on which you want to call a goal by
adding the following on the root maven.xml :
<goal name="myGoal">
<maven:reactor
basedir="${basedir}"
includes="*/project.xml"
postProcessing="false"
goals="myGoal"
ignoreFailures="false" />
</goal>
For your example, you should have :
<goal name="jboss:deploy-exploded-warfile">
<maven:reactor
basedir="${basedir}"
includes="webClient/project.xml"
postProcessing="false"
goals="myGoal"
ignoreFailures="false" />
</goal>
In your case the subprojects should have the same version number. So I
think that you can set the version (SNAPSHOT) on the root POM
(project.xml) and remove it from subprojects. I hope it will resolve
your problem...
Simon
For the problem
On Apr 11, 2005 12:10 PM, Bahaa Nasrallah <[EMAIL PROTECTED]> wrote:
> I have exactly the smae problem, can anybody who knows how to solve
> this problem reply?
>
> thanks,
> Bahaa
>
> On Apr 8, 2005 8:17 PM, Durham David R Jr Contr 805 CSPTS/SCE
> <[EMAIL PROTECTED]> wrote:
> > I've been working with multiproject for a couple of days, so while I'm
> > not exactly an expert, I feel reasonably confident with the following
> > questions.
> >
> > Basically, I'd like to end up with 1 step to deploying only changes to a
> > web application. Here's my directory structure:
> >
> > /project
> > /application
> > project.xml
> > ...
> > /webClient
> > project.xml
> > ...
> > project.xml
> > ...
> >
> > As I understand it, I need to run multiproject:something from the
> > /project directory, to "build" the multiproject. Then, I'd like to run
> > jboss:deploy-exploded-warfile from the /webClient directory. How can I
> > bundle all of this into one goal within /project/maven.xml? Something
> > like:
> >
> > The other thing I'm wondering is how manage the dependencies as
> > SNAPSHOTs. For instance, since /webClient depends on /application, I'm
> > guessing that I should have something like this in
> > /webClient/project.xml:
> >
> > <dependency>
> > <groupId>project</groupId>
> > <artifactId>application</artifactId>
> > <version>SNAPSHOT</version>
> > <type>jar</type>
> > <properties>
> > <war.bundle>true</war.bundle>
> > </properties>
> > </dependency>
> >
> > And in /application/project.xml:
> >
> > <currentVersion>SNAPSHOT</currentVersion>
> >
> > Additionally, /webClient/project.xml has:
> >
> > <currentVersion>SNAPSHOT</currentVersion>
> >
> > Then, when I cut a release, I would replace SNAPSHOT with whatever
> > version I'm releasing.
> >
> > Since I'll be actively developing both modules at once, they should be
> > SNAPSHOTs right? Currently, I'm having difficulty getting multiproject
> > to handle SNAPSHOT dependencies. It always tries to get the dependency
> > from the remote repository despite the fact that the project SNAPSHOT is
> > part of the multiproject.
> >
> > Does this make sense?
> >
> > Thanks,
> >
> > Dave
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
--
Simon BRANDHOF
Hortis - La rencontre de l'Agilit� et de l'Open-source
www.xp-suisse.org
www.hortis.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
