just make a parent POM that has <packaging>pom</packaging> and add entries
to tthe <modules> element defining as children POMs the things you want to
build. They don't have to be related in any way but if they are, they will
be built in the right order. (For example, a jar that is used in two real
applications.)

If you don't ever change the version in the dummy parent, you don't ever
have to mess with the children's <parent> element.

As a side effect, you can have some common settings in the parent if you
want to define things like what version of junit you are using or the
organization name if it is common to all your projects.

If you only want to build one of the children just run mvn from that folder.
Only that child will be built and the other children will be ignored.

Thanks.

-- Lee

On 2/3/06, Fredy <[EMAIL PROTECTED]> wrote:
>
> Hi all,
> I have asked the same question in Thread "[m2] parent pom", but nobody has
> answered, so usually it was going under ;-)
> I cannot belive, that I am the only one who's missing something like that!
>
> The multi Project mechanismus is ok for real submodules, that never used
> in another context. Because the submodules must have a
> reference to the parent.
>
> I miss a possibility to define processGroups. (Using submodules without
> ONE parent.)
>
> Example:
> module A depends on module D
> module B depends on module D
> module D depends on module C
>
> So if i develop module A and A,B,C are SNAPSHOT'S I want to call compile,
> package, install... on a process/develop Group:
>
> <processGroup>
>   <dependency>
>       <groupId>myGroup</groupId>
>       <artifactId>moduleA</artifactId>
>       <version>1.o-SNAPSHOT</version>
>       <scope>compile</scope>
>     </dependency>
>   <dependency>
>       <groupId>myGroup</groupId>
>       <artifactId>moduleB</artifactId>
>       <version>1.o-SNAPSHOT</version>
>       <scope>compile</scope>
>     </dependency>
>   <dependency>
>       <groupId>myGroup</groupId>
>       <artifactId>moduleD</artifactId>
>       <version>1.o-SNAPSHOT</version>
>       <scope>compile</scope>
>     </dependency>
> </processGroup>
>
> This is a small Example, the dependencies could be much more complex ;-)
> So a thing like a processGroup may be a very great way to save me time.
> Ok. i can write an shell or ant script doing that, but it would be nice if
> maven can do something like that.
> Do you understand me?
>
> Fredy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
-- Lee Meador
Sent from gmail. My real email address is [EMAIL PROTECTED]

Reply via email to