oops! Thanks for the clarification - I'd never had any problems
myself, but I thought I'd gotten that indication from the release
notes/web site. Long while ago now, obviously my memory isn't so good.
- Brett
On 11/09/2006, at 7:55 AM, Stephen Colebourne wrote:
Brett Porter wrote:
Didn't collections go through this (backwards-incompatible API
change, not a JDK5-ification) Îin the past for 3.0? Any
experiences that can be learned from there?
[collections] 3.0 has been FUDed with the backwards incompatible
tag ever since it was released, but it was never exactly true. The
release rewrote many classes, and tidied many APIs, but did so by
moving them into new packages. The original classes were
deprecated, so no problems...
...except that one backwards incompatible change did sneak in -
where the return type of a constant was changed. The clirr tool
would have caught it, but didn't exist then.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
