Re: Build failed in Jenkins: commons-pool #13

On 5 March 2017 at 17:27, Matt Sicker wrote: > Well something is improperly configured in Jenkins and I can't figure it > out. This project only requires Java 6 (as does the version of Maven being > used), yet something on Jenkins requires Java 7. Jenkins Maven plugin. I can

Build failed in Jenkins: commons-pool #16

See -- Started by user sebb [EnvInject] - Loading node environment variables. Building remotely on ubuntu-6 (ubuntu) in workspace Checking out

Re: [POOL][DBCP] Release plans

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

Jenkins build is back to normal : commons-pool #17

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

Build failed in Jenkins: commons-pool #15

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-4 (ubuntu) in workspace Updating

Re: Build failed in Jenkins: commons-pool #13

Well something is improperly configured in Jenkins and I can't figure it out. This project only requires Java 6 (as does the version of Maven being used), yet something on Jenkins requires Java 7. On 4 March 2017 at 15:17, Apache Jenkins Server wrote: > See

Re: [POOL][DBCP] Release plans

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

Re: [VOTE][LAZY] Migrate Commons Pool to Git

+1 Gary On Mar 5, 2017 6:22 PM, "Matt Sicker" wrote: This is a vote by lazy consensus to migrate the commons-pool subversion repository into git. We have been slowly migrating projects in Commons to git, and I'd like to migrate Pool to make it easier to perform a new release

[VOTE][LAZY] Migrate Commons Pool to Git

This is a vote by lazy consensus to migrate the commons-pool subversion repository into git. We have been slowly migrating projects in Commons to git, and I'd like to migrate Pool to make it easier to perform a new release and in general because git's easier to use nowadays thanks to its

Build failed in Jenkins: commons-pool #14

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-4 (ubuntu) in workspace Updating

[POOL][DBCP] Release plans

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

Re: [POOL][DBCP] Release plans

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

Re: [POOL][DBCP] Release plans

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