On Tue, Dec 6, 2011 at 9:56 PM, Henri Yandell <flame...@gmail.com> wrote: > On Sun, Dec 4, 2011 at 9:28 AM, sebb <seb...@gmail.com> wrote: >> On 4 December 2011 17:13, William Speirs <wspe...@apache.org> wrote: >>> What is the "rule" on when you can switch Java versions? Is going from >> >> http://commons.apache.org/releases/versioning.html >> >>> 1.4 to 1.5 too small of a version number bump to require a different >>> version of Java? Would we need to wait until 2.0 to switch to Java >>> 1.6? >> >> No, Java version changes don't require a major version bump according >> to Commons rules, though I would perhaps expect one for Java 1.3 to >> 1.6 (say). >> >> I just think that requiring Java 1.6 for a single method may be an >> unnecessary restriction of the field of use. > > +1. Generally try to stay 1.5 until a good reason. That good reason > could be a single method, it'd depend on the method :)
Reading more, this (getSQLXML) sounds like a good reason to move to Java 1.6. DB code is tied to JDBC, which is tied to version of Java. Java 5 is dead and the only reason I'd heard to consider 5 was Android, which doesn't feel like it should a big database client codebase. So +1 to moving to Java 6. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
