[
http://issues.apache.org/jira/browse/COLLECTIONS-110?page=comments#action_12413923
]
Sergei Ivanov commented on COLLECTIONS-110:
-------------------------------------------
Dear Colbert
Apparently issue tracking for Commons Collections has been migrated to JIRA
recently, so I had to copy our latest discussion postings here.
I checked out collections15 from SourceForge CVS and had a closer look at the
code. Here are my observations:
1. It apparently started as a separate project, and has never been endorsed by
ASF
2. The author(s) repackaged many classes (especially functors). This is very
bad, because it makes synchronisation with the baseline extremely complicated.
The project seems to be stalled and based on a dated stable release of
collections.
3. The overall quality of "generification" is rather good (the author(s)
obviously studied the aforementioned tutorial), but could be better.
I would really love to hear a voice of ASF committers (James?). Without any
active support from Jakarta members the "generification" project is doomed.
IMO, if this project is to be started, it should be placed into Jakarta
incubator and follow the normal evolution path. I have also got some
"generified" collections code that I'd be happy to share.
Another issue raised is: which version is to become the main branch. Having
worked in the investment banking industry for the last 4 years, I can say from
my experience that there is a huge number of legacy projects there, many of
which are still rinning on JDK 1.3. And an upgrade to a newer version of the
JDK carries with it a significant element of risk (and potential losses may
amount to millions). And there are many other long-running projects that will
require at least JDK 1.3 compatibility for years to come. Having said that, I
think the current version of collections should still be considered as the
base, and collections-1.5 codebase should be branched off it and it should
absord all changes made later on the main branch.
On the other hand, collections-1.5 may get rid of deprecated classes right at
the start. We can also use the other niceties of java 5, like varargs and
foreach, e.g.:
public AllPredicate(Predicate... predicates) {....}
I am ready to contribute to this project if there is any interest from the
community.
> [collections] Support parametized classes with commons.collections.
> -------------------------------------------------------------------
>
> Key: COLLECTIONS-110
> URL: http://issues.apache.org/jira/browse/COLLECTIONS-110
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
