Vincent Massol wrote:
>
> ----- Original Message -----
> From: "Jon Stevens" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, August 15, 2001 6:14 PM
> Subject: Re: [SUBMIT] digester logging patch
>
> > on 8/15/01 1:55 AM, "Vincent Massol" <[EMAIL PROTECTED]> wrote:
> >
> > > The problem is not so much the size of the jars that you need to bring
> in
> > > but rather the fact that you have to bring them in ...
> > >
> > > Do we agee on that need ?
> >
> > No!
> >
> > The reason why is because a few of us are working towards bringing CJAN
> into
> > Jakarta which makes the need for bringing them in on their own: zero.
>
> hum ... Jon, I was thinking about external users of our frameworks not we
> developers inside Jakarta land ...
> the majority of the users (99%) don't want to be bothered with this internal
> logging thing, they just want to use our framework and they don't want any
> additional complexity : getting log4j, configuring it, ... Agreed, it could
> be bundled with the distribution. However, commons is about frameworks, not
> applications, which means persons will take our jar (like cactus.jar) and
> bring it in their own environment ... and then ... will also need to bring
> in log4j and it's configuration.
Actually, commons is *not* about frameworks - one of the fundamental
ideas in the foundation of commons is that there would no 'most favored
nation' status. The idea (well, my view, anyway) was to find a way to
bring the richness of the Jakarta codebases together in a
'contributing-project-neutral' manner - for example, to bring together
the best of the Turbine and Struts connection pools to have a separate,
independant one that could be shared and used by all.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
Well done is better than well said - New England Proverb
