commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dion Gillard <>
Subject Re: [collections] [functor] Split functors from collections
Date Thu, 24 Nov 2005 22:23:29 GMT
+1 to the split.

Proposal A would seem to make the most sense.

I'd like to see a 'deprecation release' of collections with the
functor code marked as deprecated so that users know this is being

This would give be a big heads up about the new component and that
their build process should change.

On 11/25/05, Stephen Colebourne <> wrote:
> Commons collections is a large jar file. Some users have issue with
> that. Those users tend to complain most about the functor part, which is
> an area of more religious feeling than the rest of collections.
> I want to float the idea therefore of splitting the functors away from
> collections. This was done once before with primitives.
> Proposal A is to create a new commons proper component [functors] which
> contains the functors subpackage and the four functor *Utils classes and
> releasing commons-functors.jar. The package name would not change (this
> is as per [primitives]). This proposal works because [functors] and
> [collections] could easily be on different release schedules.
> Proposal B is to just release [collections] as two jars,
> commons-collections (no functors) and commons-collections-functor.
> Thoughts?
> Stephen
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

"You are going to let the fear of poverty govern your life and your
reward will be that you will eat, but you will not live." - George
Bernard Shaw

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message