Hi everyone,
> A big advantage of Java 1.6 over 1.5 is that the @Override annotation > also works on methods that come from an interface. That eases > refactoring a lot. > > Java 1.6 also comes with a slightly improved Collections framework. BTW: I wasn't even aware of these new, cool features... ;-) > Is that enough to warrant a jump to 1.6? Probably not. Several people > have already expressed their feelings against jumping to 1.6 anyway. > Moving on to 1.5 is what counts most IMO. FWIW, I've been using 1.6 since it got out. But I've also been using/testing with several nightly builds from a bunch of software, so this is an attitude (being a spare-time alpha/beta tester) more than a wish to use recent software versions and take the best advantage of their new features. I've only been downloading/updating my 1.4/1.5 installs in order to compile Batik every now and then (I also use 1.6 most of time) and am happy about it. The move to 1.5 makes sense IMO, but I'd be worried about a straight move to 1.6 when Batik has 1.3 minimum requirement in the latest release (Batik 1.7) and is currently pushing to 1.4 (with current SVN code which is something like Batik 1.8-pre). I've also summarized this in the scope of bug 46434 (comment 5) [1]. Cheers, Helder [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=46434#c5 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
