Multiproject uses Reactor, which does determine the correct order to build
in. I found that <jar:install> will make the project you just built
(assuming it's a JAR) available for all subsequent builds. And there's two
ways you can do it (I'm sure there's even more).
First, I added an <attainGoal name="jar:install"/> within a maven.xml in
each project directory. I usually put them in a <postGoal/> that involves a
jar:jar right before.
The other way is to specify it in the goals list in Reactor, like so:
<goal name="wuteva:build">
<maven:reactor
basedir="${basedir}"
includes="**/${pattern}/**/project.xml"
excludes="project.xml"
goals="clean,java:compile,jar:jar,jar:install"
banner="Generating"
ignoreFailures="false"/>
</goal>
Hope that helps.
Yoway Buorn
Software Engineer
Imagery Systems Engineering
GENERAL DYNAMICS
Advanced Information Systems
112 Lakeview Canyon Road
Thousand Oaks, CA 91362-5027
Tel 805 497 5074
Fax 805 497 5050
[EMAIL PROTECTED]
So one day these two muffins were baking in an oven. One muffin turned to
the other muffin and said, "Boy it sure is hot in here." The other muffin
turned to the first muffin and said, "Holy crap! A talking muffin!"
-----Original Message-----
From: Bateman, Patrick eMEDIA [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2003 5:39 AM
To: 'Maven Users List'
Subject: RE: multiproject dependencies
I know this has been answered before, but just for clarity.
When running the Multiproject goal and there is a dependency ordering
requirement, does the Multiproject analyse the sub-projects dependencies and
work out the correct order to build.
If this is correct, then how do I get Maven to use the artefacts generated
by the Multiproject goal to be included as the dependee's of the next
sub-project being built. i.e. force the Multiproject goal to only generate
SNAPSHOTs and then re-use these SNAPSHOTs within the same build.
Thanks
Pat
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 10 September 2003 08:23
To: Maven Users List
Subject: Re: multiproject dependencies
Beta10 multiproject has some bugs :-)
Use the released version.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Nathan Coast <[EMAIL PROTECTED]> wrote on 10/09/2003 04:11:51 PM:
> :)
>
> just tried using multiproject and it barfed with
>
> maven-multiproject-plugin-1.0-SNAPSHOT/plugin.jelly:149:61: <j:set> This
> tag does not understand the 'name' attribute
>
> I checked the jelly docs and set doesn't seem to take a name attribute.
>
> I was using maven beta 10. I'm rebuilding maven from cvs now to see if
> this makes a diference.
>
> [EMAIL PROTECTED] wrote:
>
> > Well, yes, since it uses the reactor.....
> > --
> > dIon Gillard, Multitask Consulting
> > Blog: http://blogs.codehaus.org/people/dion/
> >
> >
> > Nathan Coast <[EMAIL PROTECTED]> wrote on 10/09/2003 02:54:58 PM:
> >
> >
> >>Hi,
> >>
> >>Does the multiproject plugin build dependent projects in the correct
> >>order (like the reactor does).
> >>
> >>thanks
> >>Nathan
> >>
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>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]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
---------------------------------------------------------------------
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]
