Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of jak-commons-dev@m.gmane.org
 designates 80.91.229.12 as permitted sender)
Mail-Followup-To: dev@commons.apache.org
To: dev@commons.apache.org
From: =?UTF-8?B?SsO2cmc=?= Schaible <joerg.schaible@gmx.de>
Subject: Re: [dbcp] 2.0 prep
Followup-To: gmane.comp.jakarta.commons.devel
Date: Sun, 17 Oct 2010 15:57:10 +0200
Lines: 24
Message-ID: <i9evbn$mfa$1@dough.gmane.org>
References: <4CBA61AF.3090003@gmail.com>
Reply-To: joerg.schaible@gmx.de
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8Bit
Mail-Copies-To: nobody
User-Agent: KNode/4.4.5

Hi Phil,

Phil Steitz wrote:

> I just created a dbcp 1.4 legacy branch, so we can now start work
> toward dbcp 2.0 in trunk.  Pool is already off to the races.  As we
> have discussed, I would like to start exploring bringing in the
> Tomcat jdbc-pool code, split somehow between [pool] and [dbcp].
> 
> To get [dbcp] moving, I would like to make the following pom changes
> in trunk:
> 
> 0) change the groupId to org.apache.commons
> 1) change the artifactId to commons-dbcp2
> 2) change the pool dependency version to 2.0-SNAPSHOT
> 
> Both 1) and 2) may be controversial, so I want to allow people to
> weigh in before making these changes.  I know we like to avoid
> snapshot dependencies, but I don't see any other way to keep the API
> changes in synch.  Any better ideas?

All arguments have already been spoken. So, +1 to al of this.

- Jörg


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