I think the intention has been to be as backward compatible as possible with 1.9, and that's why there should still be a 1.9 and 2.0 (removing all the deprecated stuff will break tons of things). Patch releases should strive to be a 100% drop in replacement, but that's not a realistic requirement for major releases. The simplest example is adding a new method to a public interface... you need to do it sometimes, but it breaks compatibility.
As far as 1.9 goes, most apps should be fine... but I don't think we can advertise it as 100% just because changes were confined to expert level stuff (and what constitutes expert level is kind of subjective in any case). -Yonik Now hiring -- http://forms.cnet.com/slink?231706 On 11/9/05, Erik Hatcher <[EMAIL PROTECTED]> wrote: > Expert level changes are understandable. But I'm more concerned > about folks wanting to simply drop in the 1.9 JAR into an existing > application without recompilation. Where do we break this? And is > there no way to get to binary level compatibility? If not, then our > next release version should just be 2.0 and skip 1.9, don't ya think? > > Erik --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
