commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergei Ivanov (JIRA)" <>
Subject [jira] Commented: (COLLECTIONS-110) [collections] Support parametized classes with commons.collections.
Date Thu, 01 Jun 2006 18:39:30 GMT
    [ ]

Sergei Ivanov commented on COLLECTIONS-110:

> The choice to use new packages was I believe a recommendation
> from us, so as to ensure that both the generic and non-generic
> versions can be in the classpath at the same time. 

If they only renamed org.apache.commons.collections to net.sf.collections15, that would still
be manageable. However, what I was pointing to is, for example, that all predicates were moved
from ...functors package under net.sf.collections15.functors.predicate package. Also, some
new classes were introduced (e.g. AbstractPredicateDecorator, although in my opinion it's
well justified, because it reduces code duplication). Such divergence will make propagation
of changes/fixes from "classic" collections much more difficult.

> [collections] Support parametized classes with commons.collections.
> -------------------------------------------------------------------
>          Key: COLLECTIONS-110
>          URL:
>      Project: Commons Collections
>         Type: Bug

>  Environment: Operating System: other
> Platform: Other
>     Reporter: Colbert Philippe

> It's time to create a parallel version of commons.collections to support 
> parametized classes of each container class and abstract class.  It's not that 
> hard.  There is a 23 PDF document on Sun Java website describing in detail how 
> it should be done and what to watch out for.
> I already converted a few classes from commons.collection privately for my own 
> needs.  Once you get the hang of it, it's a rather quick process.
> I am even willing to volunteer my time to do some more but I need the 
> collaboration of some of the original programmers to watch over things.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

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

View raw message