On 6/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
You touched on a good point here. I have a similar situation where I
have multiple modules that don't share the same release structure yet I
would still like to have them use the same parent POM to inherit certain
project info.
Has anyone defined a Parent POM like that and just not included the
"module" tags in it? Or would that be considered a Super POM instead?
--Rudy
In my opinion, this is how you should do it. Lot of people don't
realize it but a super pom and modules are two different concepts. So
if you want to share some values just use a super pom (using the
parent tag) which doesn't declare any modules. For instance, I use a 3
level pom hierarchy and it works like a charm.
-----Original Message-----
From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 18, 2006 2:32 PM
To: Maven Users List
Subject: Re: conceptual problem in multi-module project?
>
> That is the point. In order to build m2, I have to build the whole
> project. If m2 is still in development (ie, some tests still fail),
> I can't build m2 separately.
If m2 and m1 doesn't share the same release cycle, they shouldn't be
sibling modules. The purpose of modules is to separate a big project
in small subprojects. Instead just declare a SNAPSHOT m2 dependency in
you m1 pom. Modules dependencies is the same as Eclipse project
dependencies. If one project doesn't compile than of course all the
other projects depending upon this one won't compile either.
---------------------------------------------------------------------
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]
