the code NEEDS to change though, and not in a backwards compatible way. Do whatever is appropriate with version numbers to indicate that non-binary compatible changes are coming.
Cheers, -L On Sun, Mar 8, 2009 at 6:04 AM, Stephen Colebourne < scolebou...@btopenworld.com> wrote: > Dan Fabulich wrote: > >> Henri Yandell wrote: >> >> The Java5 version is more up for debate. If the API is no longer >>> compatible, then we start to lean to 2.0. Especially as calling it 2.0 >>> allows for more of an overhaul of API. >>> >> >> The the API in the "java5" branch is backward compatible; the generics and >> varargs are erased at compile time. Of course, the code has to be compiled >> with target=1.5, but on a Java 1.5 VM you could swap it in and not notice >> the difference. >> > > Check javap method signatures, or use clirr. > > > Stephen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
