commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 39538] - [collections] Support parametized classes with commons.collections.
Date Wed, 10 May 2006 14:09:44 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39538>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39538





------- Additional Comments From cp1965@ROGERS.com  2006-05-10 14:09 -------
You should definitely branch out.  Support for non-parametric classes must be 
maintained for a long time to come.  I suggest starting the newer branch as 
commons.collections v5 to copy the Java 1.5 (also called Java 5 by some).

Taking the plunge is the best way to go.  I did and was suprised to how quickly 
things go.  The team should agree on a few basic principle which are also 
outlined in a PDF document distributed by Sun on their website (named generics-
tutorial.pdf).

I suggest starting with the abstract classes.  Have a review between developers 
to catch oversights.  Then go on to modify 2 or 3 containers and format testing 
(JUnit).  The tests should be straightforward.  It's a matter of testing 
derived type compatibility.  Once the first 2 or 3 containers done and tested, 
the rest will go very quickly.  

This project can be done in less than 1 month confortably.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
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