On 10/28/07, Stephen Kestle <[EMAIL PROTECTED]> wrote:
> NB!!! Don't submit patches for CollectionUtils --- I have it 90%
> complete, and will find time to do the other 10% if people want to see
> it (are people actually using the generics branch? I am, but then I know
> it's as good as my own co
But can't the library be first moved to a point where one can say the
new releases will run only on 1.5+ JVM, and then
gradually/slowly/carefully re-work/generify the internals as necessary
? So at least this won't constrain any new development effort from
using all the goodies in 1.5+, and yet
The plan is for non backwards compatibility, as there are too many
things that don't make sense for generics, and some things that plain
don't work. The Map coercion methods become silly, and TransformedMap
can't conform to the map interface in it's current form (is that the
right one?).
Hav
Collections has been on my long-term want-to-get-involved-with list too, but
I don't see a feasible technical plan for the desired generics refactoring.
In the past when I've done similar stuff I've found that you can't really do
it incrementally. If someone could throw together a roadmap that expl
Why don't we set up a page for all of Commons to discuss the
JDK5-ization (it's a word) of each of the components (if need be)? I
wouldn't mind helping with Collections.
On 10/26/07, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
> Brian A. Egge wrote:
> > What I would like, is a drop in replaceme
Brian A. Egge wrote:
What I would like, is a drop in replacement, with binary backwards
compatibility with the 1.4 version. I want everything in the same
package name, and to have the same names.
Not all parts of [collections] can be generified in this manner. For
example, MultiMap and IIRC Bag
> I seem to recall there being a strong view that we didn't want
> Collections to be glossy painted with 1.5, but that whole APIs should
> be rethought as they contained workarounds to the lack of generics.
But can't the library be first moved to a point where one can say the
new releases will run
Afaiu, the main reluctance is that no one has stepped up and started
organizing it.
I seem to recall there being a strong view that we didn't want
Collections to be glossy painted with 1.5, but that whole APIs should
be rethought as they contained workarounds to the lack of generics.
+1 on pullin
Maybe we should set up a wiki page to discuss this 1.5 problem for
collections (and maybe other projects). We should outline why we have
been reluctant as of yet to "genericize" collections (binary
compatibility, serialization issues, etc.). That way folks don't have
to try to search through the
Hi,
What's the status of the JDK 1.5 branch? It seems the developers are split as
to if it's a good thing, and if so, if the API should be different or the same.
Most advice I see says to use the collections15 project on SourceForge.
What I would like, is a drop in replacement, with binary
10 matches
Mail list logo
