commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <craig...@apache.org>
Subject Re: [collections] collections depends on lang? (RE: cvs commit: jakarta-commons/collections/src/java/org/apache/commons/collections ClassMap.java)
Date Fri, 25 Oct 2002 22:39:33 GMT


On Fri, 25 Oct 2002, Steve Downey wrote:

> Date: Fri, 25 Oct 2002 15:35:06 -0400
> From: Steve Downey <steve.downey@netfolio.com>
> Reply-To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> Subject: Re: [collections] collections depends on lang? (RE: cvs commit:
>     jakarta-commons/collections/src/java/org/apache/commons/collections
>     ClassMap.java)
>
> When libraries are too small, you start to have to make bad decisions about
> coupling. There are natural ways for lang, collections, beanutils and a few
> others to interact. Coupling them is probably better than duplicating the
> behavior. OTOH, it does introduce more management difficulties, because the
> releases would need to be coordinated.
>
> It is interesting to note that the releases of many of these projects,
> although coordinated separately, do tend to come in waves. The release bug is
> contagious.
>

I took a crack at one way to deal with the coupling problems, by creating
the "combo" directory in the jakarta-commons workspace.  The basic idea
was to allow a developer to create an all-in-one JAR file with your
favorite tagged versions of *all* the released Commons packages -- the
default would be the latest released version of each package.  My thinking
was that, whenever one of the constituent packages did a release, the
release manager would also do an updated commons-combo release.

As an extra added benefit, the build script creates consolidated Javadocs
for the included packages -- something that I've found invaluable in its
own right, completely separate from the combined JAR file.

If you'd like to help me explore whether this would be a useful thing to
work on, feel free to pitch in - I'm sure that the build.xml file there
now is probably somewhat stale, and the CVS checkin log messages for
build.xml mention some FIXME items that weren't done in the first place.

>
>
>
> On Friday 25 October 2002 01:35 pm, Henri Yandell wrote:
> > *chants*
> > commons-core commons-core
> > */chants*
> >
> > :)
> >

Or maybe  commons-combo ... commons-combo ... :-)


Craig


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


Mime
View raw message