Re: [POOL][DBCP] Release plans

2017-03-06 Thread Matt Sicker 
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 <
https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/jdbc_42.html>.
I'm not sure if that would require a new major version (3.0) or if we'd
just support it in 2.3 or 2.4.

On 6 March 2017 at 03:15, Romain Manni-Bucau  wrote:

> 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 upgrade to Java 8 for dbcp 2.3,
> but
> > > it's also worth mentioning if needed.
> >
> > Is there any reason - apart from the age of Java 6 - to make Java 7 the
> > minimum for Pool?
> >
> > Tomcat 8 uses DBCP 2 and Pool 2 and - because it implements parts Java
> > EE 7 specification, has to run on Java 7. An upgrade to Java 8 would be
> > an annoyance but one the Tomcat project could work around if it had to.
> >
> >
> Same for TomEE* (openejb part too which runs without tomcat) which would
> mean for both projects to fork (repackage) pool and dbcp
>
>
> > Mark
> >
> > >
> > > On 5 March 2017 at 11:59, Pascal Schumacher 
> > > wrote:
> > >
> > >> 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 starting a release candidate for pool 2.4.3. After
> > that,
> > >>> we
> > >>> can upgrade DBCP to pool 2.4.3 and do a release of DBCP to 2.2.
> > >>>
> > >>>
> > >>
> > >> -
> > >> 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
> >
> >
>



-- 
Matt Sicker

Re: [POOL][DBCP] Release plans

2017-03-06 Thread Romain Manni-Bucau 
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 upgrade to Java 8 for dbcp 2.3, but
> > it's also worth mentioning if needed.
>
> Is there any reason - apart from the age of Java 6 - to make Java 7 the
> minimum for Pool?
>
> Tomcat 8 uses DBCP 2 and Pool 2 and - because it implements parts Java
> EE 7 specification, has to run on Java 7. An upgrade to Java 8 would be
> an annoyance but one the Tomcat project could work around if it had to.
>
>
Same for TomEE* (openejb part too which runs without tomcat) which would
mean for both projects to fork (repackage) pool and dbcp


> Mark
>
> >
> > On 5 March 2017 at 11:59, Pascal Schumacher 
> > wrote:
> >
> >> 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 starting a release candidate for pool 2.4.3. After
> that,
> >>> we
> >>> can upgrade DBCP to pool 2.4.3 and do a release of DBCP to 2.2.
> >>>
> >>>
> >>
> >> -
> >> 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
>
>

Re: [POOL][DBCP] Release plans

2017-03-06 Thread 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 upgrade to Java 8 for dbcp 2.3, but
> it's also worth mentioning if needed.

Is there any reason - apart from the age of Java 6 - to make Java 7 the
minimum for Pool?

Tomcat 8 uses DBCP 2 and Pool 2 and - because it implements parts Java
EE 7 specification, has to run on Java 7. An upgrade to Java 8 would be
an annoyance but one the Tomcat project could work around if it had to.

Mark

> 
> On 5 March 2017 at 11:59, Pascal Schumacher 
> wrote:
> 
>> 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 starting a release candidate for pool 2.4.3. After that,
>>> we
>>> can upgrade DBCP to pool 2.4.3 and do a release of DBCP to 2.2.
>>>
>>>
>>
>> -
>> 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

Re: [POOL][DBCP] Release plans

2017-03-05 Thread Gary Gregory 
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 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 Schumacher 
> wrote:
>
> > 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 starting a release candidate for pool 2.4.3. After that,
> >> we
> >> can upgrade DBCP to pool 2.4.3 and do a release of DBCP to 2.2.
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>
>
> --
> Matt Sicker 
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition



JUnit in Action, Second Edition



Spring Batch in Action


Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [POOL][DBCP] Release plans

2017-03-05 Thread Matt Sicker 
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 Schumacher 
wrote:

> 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 starting a release candidate for pool 2.4.3. After that,
>> we
>> can upgrade DBCP to pool 2.4.3 and do a release of DBCP to 2.2.
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Matt Sicker

Re: [POOL][DBCP] Release plans

2017-03-05 Thread Pascal Schumacher 

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 starting a release candidate for pool 2.4.3. After that, we
can upgrade DBCP to pool 2.4.3 and do a release of DBCP to 2.2.




-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [POOL][DBCP] Release plans

2017-03-05 Thread Gary Gregory 
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 pool 2.4.3 and do a release of DBCP to 2.2.
>
> --
> Matt Sicker 
>