Hi,
What I don't understand, compared to writing really useful information on the
mailing list, how more difficult is it to keep the guides and FAQs on the page
in shape? IMHO, if we could streamline the process of updating the guides and
FAW (wiki like), the documentation could be improved a lot. But I guess the
guides are in apt format, checked in in cvs, right?
Anyway, this is something that should be put into the multimodule-guide, which
does not exist yet.
_ __ _ _
//\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com
`- `
Andreas Ebbert-Karroum
Software Design Engineer - Nokia Networks Services / Middleware
phone: +49-211-94123928, fax: +49-211-9412-3838
Heltorfer Straße 1, 40472 Düsseldorf, Germany
----------------------------------------------------------------------
This message is confidential. If you have received this message in error,
please delete it from your system. You should not copy it for any purpose,
or disclose its contents to any other person. Internet communications are
not secure and therefore Nokia GmbH does not accept legal responsibility
for the contents of this message as it has been transmitted over a public
network. Thank you.
Nokia GmbH, Nokia Networks is a German Company. Further information
about 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 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 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:
> <modules>
> <module>module3</module>
> <module>module2</module>
> <module>module1</module>
> </modules>
>
>Then make sure you have in module1/pom.xml:
><?xml version="1.0" encoding="iso-8859-1"?> <project>
> <parent>
> <groupId>blah</groupId>
> <artifactId>parent</artifactId>
> <version>1.0.0</version>
> </parent>
> <modelVersion>4.0.0</modelVersion>
> <groupId>blah</groupId>
> <artifactId>module1</artifactId>
> <packaging>jar</packaging>
> <version>1.0.0</version>
> <dependencies>
> <dependency>
> <groupId>blah</groupId>
> <artifactId>module3</artifactId>
> <version>1.0.0</version>
> <scope>compile</scope>
> <type>jar</type>
> </dependency>
>
>And then issue a simple "mvn package" command from parent directory.
>This will also place the resulting jar in the module1/target directory.
>
>Wayne
>
>
>On 3/17/06, Pierre Monestie <[EMAIL PROTECTED]> wrote:
>> Hello,
>> I've been looking all over for this and could not find any answer:
>> In a multi module project how can I, from the parent level, build a
>> specific module?
>> Going into the child I want to build does not work as it
>refers to a parent.
>>
>> For example I have:
>> parent
>> --module1 (depends on module3)
>> --module2
>> --module3
>>
>> and I just want to build module1.
>> Tell me this is possible plz :)
>> Thanks in advance,
>> Pierre
>>
>> ---------------------------------------------------------------------
>> 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]
