From: "Peter Donald" <[EMAIL PROTECTED]>
On Fri, 10 May 2002 03:02, Nicola Ken Barozzi wrote:
> > I honestly think that what Avalin has done with Excalibur is really
> > stretching the definition of sofware module a bit too far.
> >
> > What is the *need* for a division of packages in different root dirs?
Can't
> > just a specializes jar task divide them upon jarring?
>
> What is the need of ever having separate directories at all? Why can't
cocoon,
> avalon, ant, james, turbine, struts etc live in one source hierarchy?
Yeah, why? (Honestly the question came to me)
> The main reason is it allows Isolation and avoids accidental dependencies.
> People have to make a conscious decision to add in new dependencies rather
> than making a conscious decision not to add in dependencies. ie Some of
our
> components were coupled to other components via one class that wasn't een
> needed or used. The current arrangement avoids this.
Ahhh, now I get it. It's all about (correcting me if I'm wrong) /forcing/
developers to make /concious/ decisions on dependency.
I agree with the need, it's valuable. But using separate dirs for this is
more a technical thing.
> Also in the past sometimes someone would break the build - now it only
effects
> one component rather than a whole bunch.
Again, this is a technical thing.
I can still split the packages in the build and build them separately.
I think that Centipede will need to make it able to use any of these
approaches, and your explanation makes the motivation clear to me, thank you
:-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
