On Wed, Jan 14, 2009 at 9:18 AM, Mark Thomas <ma...@apache.org> wrote: >> -----Original Message----- >> From: Niall Pemberton [mailto:niall.pember...@gmail.com] >> Sent: 14 January 2009 01:38 >> To: Commons Developers List >> Subject: Re: [DBCP] Moving towards a 1.3 release >> >> On the issue of not building with JDBC 4.0 / 1.6 JDK (DBCP-191) and >> creating a compatible release with previous JDKs (1.4/1.5) then we >> should be able to set the source/target compiler options. The main >> issue would then be ensuring that other JDK 1.6 features didn't leak >> into the rest of the code base. DBCP seems to already have a mechanism >> in place that deals with the JDBC 2.0/3.0 incompatibilities with the >> source code being "marked up" and options in the ant build to detect >> the JDBC version and comment out portions of the code. We could extend >> this to the JDBC 4.0 features. This should enable it to be tested on >> previous JDK versions, even if the release is created using JDK 1.6. I >> am willing to try to get this working this week - I'm a bit short on >> time, but hopefully by the weekend. > > Just so we don't duplicate effort, I have the DBCP-191 patch applied and > working (with a few tweaks). I am planning on running some tests with it > with multiple JDK versions today before committing it.
OK great Niall > Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
