commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <>
Subject Re: [collections] JDK1.5
Date Thu, 24 Jun 2004 15:34:05 GMT

Just to ask the village idiot question, why would moving to 1.5 mean
losing 1.4 support?

>From what I understood (which is not much), 1.5 maintains
binary-compatibility with 1.4 for Collections as far as generics go, but
not compile-time (obviously).

We just need to have a process in which Collections is tested in 1.2, 1.3,
1.4 and 1.5, but write it under 1.5?

I imagine it would bloat the API for 1.4 with all the generated methods.


On Wed, 23 Jun 2004, Stephen Colebourne wrote:

> While release 3.1 is being tidied up (still time to vote ;-), I thought I'd
> just put out a note about JDK1.5.
> One of the key enhancements in JDK1.5 is generics which allows typed classes
> using the angle bracket notation. The biggest area this impacts is
> collections. Clearly questions have to be raised as to how this affects
> [collections].
> So far, I have done no work to see if [collections] will compile under
> JDK1.5. My expectation is that it will, but there are no guarantees.
> To take full advantage of generics will involve a considerable rewrite of
> [collections]. It will affect every class, and produce a version that only
> compiles on JDK1.5. I have no doubt that Sun spent many mandays changing the
> JDK classes to achieve this update.
> Personally, I have no plans to update [collections] to JDK1.5 (no itch, too
> much effort). If anyone else does, feel free to come in and either change
> [collections], or (more likely) create a new [collections15] project.
> Stephen
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message