commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <>
Subject Re: [VFS] Analysis of binary compatibility breaks between 1.0 and 2.0; release strategy
Date Wed, 17 Nov 2010 07:17:47 GMT

On Nov 16, 2010, at 4:19 PM, sebb wrote:

> On 17 November 2010 00:06, ralph.goers
> <> wrote:
>> I'm not sure why the tool didn't catch it, but a few methods now return
>> Map<String, Object> where they previously returned Map. I didn't check for
>> generics other than "Map<".
> Surely these are equivalent at run-time?
> Generics are a compile-time feature.

See and then
take a look at the several changes made to add generics to Comparable.  These changes don't
seem to be binary compatible. I'm surprised they didn't show up in the report you ran.

I've found several other articles that describe how, under certain circumstances, type erasure
can result in a different type being used than existed in a prior, non-generified version
of the code. I've not fully inspected all teh changes to determine if any of those cases are

I'm not suggesting we change these. Since we are adopting Java 5 I would prefer to change
these now and move forward.

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

View raw message