Henri Yandell wrote:
Why not just start a branch within Collections?
I don't see why this is a new component, are we going to be advising
people to use Collections 3.x on JDK 1.5+ for any reasons other than
legacy or instability of our generified version?
My view is to make a collections-generics branch in collections with a
view to it being Collections 4.0.
Because commons isn't like other OSS projects. We can't go around
changing our APIs freely, even between major versions. Its a simple case
of us being at the bottom of the stack of jars. If we do change an API,
any API then jar hell ensues because higher OSS projects will clash on
their required versions of [collections].
Thus, it has to be a new package, and this is best thought of as a new
component.
(Compare this with the JDK where they had to jump through ridiculous
hoops to make generics fully backwards-compatible, and created a
half-arsed mess in the process...)
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
