ut the Company is available from its principal offices at
> > Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the
> > website at http://www.nokia.com/
> > --
> >
> > >-Original Messa
ww.nokia.com/
> --
>
> >-Original Message-
> >From: ext Wayne Fay [mailto:[EMAIL PROTECTED]
> >Sent: 18 March, 2006 06:18
> >To: Maven Users List
> >Subject: Re: multimodule building
> >
&
What's wrong with Wayne's first suggestion?
module1 *depends* on module3, so you *must* build module3 at some point
in time:
cd module3
mvn install
However now this module is built and the jar placed somewhere that
module1 can find it (under $HOME/.m2/ as it happens). You can therefore
build
a.com/
--
>-Original Message-
>From: ext Wayne Fay [mailto:[EMAIL PROTECTED]
>Sent: 18 March, 2006 06:18
>To: Maven Users List
>Subject: Re: multimodule building
>
>A few ways to do this...
>
>Assume you're starting from parent dire
I personally have never had any desire to perform a partial build as
you desire. So I have no idea if it is possible and how it would be
configured. ;-)
If you figure it out, please do let the rest of us know.
Wayne
On 3/17/06, Pierre Monestie <[EMAIL PROTECTED]> wrote:
> Wayne,
> The second wa
Wayne,
The second way you describe is the way my project is defined.
Assume I have a couple extra modules defined this way and I only want
to build module1. If I issue mvn package all the modules will be build
correct? My question is: Is there a command line switch to tell mvn to
build only module1
A few ways to do this...
Assume you're starting from parent directory...
cd module3
mvn install
cd ..
cd module1
mvn package
This will result in module1 being built and the resulting jar placed
in module1/target.
OR
Add to parent/pom.xml:
module3
module2
module1
Then make sur
