commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne" <scolebou...@btopenworld.com>
Subject Re: [collections] Size and scope issues
Date Mon, 03 May 2004 09:00:13 GMT
From: "robert burrell donkin" <robertburrelldonkin@blueyonder.co.uk>
> between open source projects. there are a few of ASF projects who are 
> refusing to use any jakarta commons components on principle now for 
> this reason. (they want small, tight libraries.)
Can you specify which? This has been mentioned before without clarity.

Stephen


> On 3 May 2004, at 00:41, Stephen Colebourne wrote:
> 
> > So what problem are we solving? Adding extra jar files alongside the
> > complete built one creates classpath problems for users, an old 
> > version of
> > the 'all' jar overriding a later version of the 'part' jar or vice 
> > versa.
> > General chaos and confusion.
> >
> > People so have the ability to build their own jar files with just the
> > classes they need.
> >
> > Oh, and I'd also suggest that more jar files does involve more work
> > (maintaining and releasing), and there's a distinct lack of active
> > committers on collections as it is ;-)
> >
> > Stephen
> >
> >> On 24 Apr 2004, at 04:33, Craig R. McClanahan wrote:
> >>> A neat ideal, but perceptions of "really common" versus "rarely used"
> >>> seem to be awfully personal.  Kinda reminds me of earlier commons-dev
> >>> discussions trying to create a "commons core" JAR that included all 
> >>> of
> >>> the "really common" commons JARs, and none of the others.  Needless 
> >>> to
> >>> say, there was no consensus on what the contents should be :-).
> >
> > From: "robert burrell donkin" <robertburrelldonkin@blueyonder.co.uk>
> >> i wonder whether it might be possible to separate out a core jar
> >> containing just the basic interfaces and then split the 
> >> implementations
> >> into several themed jars. i still think that this should be in 
> >> addition
> >> to releasing a single jar containing everything, though.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message