What are the general opinions on maintaining a generic fork of Commons
Collections?

My company has a some what sizable portion refactored or adapted into
generic compatibly that I may be able to get released under the Apache
License. Would such a project be welcomed by the community such that
collections developers would be willing to provide feedback / advice to
myself and other interested parties?

Aside from breaking with backwards compatibility and migration compatibility
with the Java Collections Framework, are there other reasons why this hasn't
been done?

There is a source forge project that once had a go at this (
http://sourceforge.net/projects/collections/develop), but their commit logs
ended in 2007. I know of no other related projects. Are there any?

--
Grant Overby
Senior Developer
FloorSoft, Inc.

Often people, especially computer engineers, focus on the machines. They
think, "By doing this, the machine will run faster. By doing this, the
machine will run more effectively. By doing this, the machine will something
something something." They are focusing on machines. But in fact we need to
focus on humans, on how humans care about doing programming or operating the
application of the machines. We are the masters. They are the slaves. --
Yukihiro Matsumoto

Reply via email to