commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <ggreg...@seagullsw.com>
Subject RE: [combo] Commons Core release?
Date Thu, 14 Aug 2003 16:15:50 GMT
I like the idea of a combo Jar but unless all released components are in
there, you will always have someone not happy because you'll still need > 1
jar.

I would also expect that is combo jar is not just a lump but a "certified"
lump which works as a whole. IOW, the project should have some tests to
validate any component dependencies and side effects.

Gary

> -----Original Message-----
> From: Craig R. McClanahan [mailto:craigmcc@apache.org]
> Sent: Wednesday, August 13, 2003 23:26
> To: Jakarta Commons Developers List
> Subject: Re: [combo] Commons Core release?
> 
> On Thu, 14 Aug 2003, Tetsuya Kitahata wrote:
> 
> > Date: Thu, 14 Aug 2003 15:14:10 +0900
> > From: Tetsuya Kitahata <tetsuya@apache.org>
> > Reply-To: Jakarta Commons Developers List <commons-
> dev@jakarta.apache.org>
> > To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> > Subject: Re: [combo] Commons Core release?
> >
> >
> > On Thu, 14 Aug 2003 15:58:45 +1000
> > "Vikram Goyal" <v.goyal@uq.edu.au> wrote:
> >
> > > > -1 on any combination.  Core / Combo - whatever.  I think it is a
> bad
> > > > idea.
> > > Agree with you that it is a bad idea. Commons was supposed to be it.
> > > Its like trying to factor out a "Commons" out of Commons. I can see
> > > the nightmare and the trouble people will have trying to understand
> > > what a "Combo" is out of Commons. Developers are sensible enough to
> > > realise and factor out common jars. Agreed that it takes time but hey,
> > > thats what we are paid for.
> >
> > I knew that these kind of objections would occur if we thought
> > this package *in* "Jakarta"-Commons Dev list.
> >
> >
> > Briefly, ... How about Apache Commons?
> >
> > Keep the tiny commons.jakarta packages as they are and Apache
> > Commons (http://commons.apache.org/) provides the mixture of
> > Jakarta-Commons, DB-Commons, XML-Commons etc.... Perfect! ;-)
> >
> > Jakarta-Commons would be as it is ... no change.
> >
> >
> 
> Nobody is talking about eliminating the individual releases.  The question
> is whether or not we should offer an *additional* combination package of
> some sort, and what it should contain.  One can certainly extend the
> concept recursively beyond Jakarta Commons, but something like this is
> going to align on language lines anyway -- and Jakarta Commons is already
> only about Java based packages.
> 
> For those who wonder why such a combination JAR is important, please hang
> around on the user lists, not just the developer lists :-).
> 
> > -- Tetsuya (tetsuya@apache.org)
> >
> >
> 
> Craig
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message