Isn't it possible to use something like that :
For example if w1 use c1 and c3, in the pom of w1 use :
<modules>
<module>../c1</module>
<module>../c3</module>
</modules>
I think you could even put that into a profile in order to allow recursive
build or not.
Gilles
> -----Original Message-----
> From: Chris Bredesen [mailto:[EMAIL PROTECTED]
> Sent: 19 January 2006 02:42
> To: [email protected]
> Cc: [EMAIL PROTECTED]
> Subject: Transitive "sibling" builds
>
> Hello All,
>
> Just subscribed, and I wanted to revisit the discussion that took place
> regarding the above topic in this thread:
> http://www.mail-archive.com/[email protected]/msg32502.html
>
> There seems to be a lot of resistance from the community (lack of
> understanding, maybe) to implementing this sort of transitive build
> mechanism. I, too, do exactly what the original poster does, and the lack
> of support for this is the only real reason I haven't adopted Maven2 as my
> build tool of choice. I get closer each time, but since there's no way to
> build an entire WAR file in one shot, I have to give it up. I realize it
> CAN be done, but it seems that the WAR file has to be the parent of all
> its
> components.
>
> I wanted to add my own experience into this discussion, and possibly even
> spur enough information to contribute myself. I have my enterprise laid
> out
> as such, made of webapps (w) and components (c):
>
> w1
> w2
> w3
> c1
> c2
> c3
> c4
> c5
>
> Each of the webapps may use any of the components as dependencies, along
> with a slew of off-the-shelf API's. The problem for me is that these
> components can have only one parent directory. I have no way to
> separately
> build w1 and w2. Unless I'm missing, something, we'd need sibling
> communication in order to make this work.
>
> Currently each Ant buildfile knows which components are needed, but has no
> idea if they need to be built or not, thus causing me to build everything
> each time I compile. To avoid this, I also maintain Eclipse projects (one
> per app, not one big one) which have project-level dependencies on each
> other. This makes the local development compilation very fast, but I have
> to maintain both the Eclipse metadata AND the Ant buildfiles.
>
> Maven addresses all of this (I really love the Maven2 plugin for Eclipse),
> but since there's no support for sibling transitive builds, there is no
> way
> to just grab all the source and compile w1 or w2 in one shot. Eventually
> I'd like to use Continuum as well.
>
> If I'm missing something here, I'd sure like to know about it. If I can
> contribute and make this happen, I'd love to, when time permits. I fear
> I'd
> have a lot of catching up to do, though. Perhaps I can work on some
> documentation at the very least.
>
> Thoughts?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
