On 14/01/2009, sebb <seb...@gmail.com> wrote: > On 13/01/2009, Mark Thomas <ma...@apache.org> wrote: > > > > From: sebb [mailto:seb...@gmail.com] > > > > > > > > Looks like some of the changes to the JDBC API mean that it is not > > > possible to create a single version of DBCP which is compatible with > > > both Java 1.4 and 1.6. > > > > > > Will that mean moving DBCP to a minimum of Java 1.6? > > > Or can it be made compatible with 1.5 and 1.6? > > > What are the plans for supporting Java 1.4 and 1.5? > > > > > > I don't actually use (or plan to use) DBCP, I'm just trying to ensure > > > that it's clearly stated what solving the problems for Java 1.6 would > > > mean for earlier Java releases. > > > > > > I haven't looked at what this might mean yet but I see no issue with > > dropping support for 1.4 if that is required. I would be more concerned > with > > dropping 1.5 support. > > > > > I would be happy with dropping 1.4 support if that is required, but I > agree that 1.5 support should not be dropped yet. > > By the way, it looks like the JBDC3 flags could be removed unless > there is any need to support a version of Java older than 1.4 - which > seems very unlikely. >
Is the intention to improve DBCP or just get it to compile and run under 1.6? If the former, then there are a few Eclipse and Findbugs warnings that could be addressed, and the calls to the deprecated SQLNestedException could be recoded as per the deprecation explanation. I can help with some of those. > > > > Mark > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
