For Pool, I'm not exactly sure why we need a Java 6 compatible
implementation for the next minor version (2.5). We've had the EOL
discussion before, and even Java 7 is at that point.
The only reason I'd look at updating DBCP to use Java 8 is to support JDBC
4.2 <
2017-03-06 10:06 GMT+01:00 Mark Thomas :
> On 05/03/17 18:21, Matt Sicker wrote:
> > I'm also thinking we might want to upgrade to Java 7 for pool 2.5 as dbcp
> > 2.x has required it from the beginning. I'm not exactly sure if anything
> > JDBC changed in Java 8 to warrant an
On 05/03/17 18:21, Matt Sicker wrote:
> I'm also thinking we might want to upgrade to Java 7 for pool 2.5 as dbcp
> 2.x has required it from the beginning. I'm not exactly sure if anything
> JDBC changed in Java 8 to warrant an upgrade to Java 8 for dbcp 2.3, but
> it's also worth mentioning if
I am +1 to making Java 7 the hard minimum for [pool] and [dbcp] on the next
minor release.
I'd love:
- to see (and use) a fresh release of [pool] followed by [dbcp]
- update to Java 7
Gary
On Sun, Mar 5, 2017 at 10:21 AM, Matt Sicker wrote:
> I'm also thinking we might want
I'm also thinking we might want to upgrade to Java 7 for pool 2.5 as dbcp
2.x has required it from the beginning. I'm not exactly sure if anything
JDBC changed in Java 8 to warrant an upgrade to Java 8 for dbcp 2.3, but
it's also worth mentioning if needed.
On 5 March 2017 at 11:59, Pascal
Great new. :)
As far as I remember there were various request for DBCP 2.2 (and we
would like to update to pool 2.4.3 at work).
Thank you very much,
Pascal
Am 05.03.2017 um 18:30 schrieb Matt Sicker:
I've started a lazy vote to migrate Pool to Git. After that, I'd like to
take a whack at
Great news Matt. Thank you for driving this effort.
Gary
On Mar 5, 2017 6:30 PM, "Matt Sicker" wrote:
> I've started a lazy vote to migrate Pool to Git. After that, I'd like to
> take a whack at starting a release candidate for pool 2.4.3. After that, we
> can upgrade DBCP to