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 paulus.benedictus@gmail.com
 designates 209.85.212.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=jr5GOEQ6nNC4Vmd4u2p5BNHn+2W/h9Rj8VnOBPrf856XKXstL5ksziRlqrV9f4ObNh
         a0KcKxNkc86T9xwd5qUpqTL9kpcpYc/mN+0NpiNSirkjRZnP6aZKBfmA0Vzx/0loQ45+
         6CbH8ay/YHOLXWXLySU79+f20eZeDvOi75v48=
MIME-Version: 1.0
Sender: paulus.benedictus@gmail.com
In-Reply-To: <AANLkTi=u+Tf-9D3qZsEFdzA8Yvcm4WSnCaNbJ6hB-Ytg@mail.gmail.com>
References: <4CBA61AF.3090003@gmail.com>
	<i9evbn$mfa$1@dough.gmane.org>
	<4CBB17AD.7050406@gmail.com>
	<AANLkTi=u+Tf-9D3qZsEFdzA8Yvcm4WSnCaNbJ6hB-Ytg@mail.gmail.com>
Date: Sun, 17 Oct 2010 11:10:46 -0500
Message-ID: <AANLkTinY0gS5JeYo9RS5q1ng8HaEO-xHjyaMLmidcFkF@mail.gmail.com>
Subject: Re: [dbcp] 2.0 prep
From: Paul Benedict <pbenedict@apache.org>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It makes perfect sense if you want multiple versions of DBCP on the
classpath. We had that discussion with Lang 3 as well.

Paul

On Sun, Oct 17, 2010 at 10:52 AM, Simone Tripodi
<simone.tripodi@gmail.com> wrote:
> Hi Phil,
> I'm sure the build will be broken at least at the beginning, this
> morning I migrated the commons-pool pom metadata and package.
> Please let me know if I can be helpful on dbcp too, thanks in advance.
> Have a nice day,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Sun, Oct 17, 2010 at 5:35 PM, Phil Steitz <phil.steitz@gmail.com> wrot=
e:
>> On 10/17/10 9:57 AM, J=F6rg Schaible wrote:
>>>
>>> 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. =A0Pool is already off to the races. =A0As w=
e
>>>> 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. =A0I know we like to avoid
>>>> snapshot dependencies, but I don't see any other way to keep the API
>>>> changes in synch. =A0Any better ideas?
>>>
>>> All arguments have already been spoken. So, +1 to al of this.
>>
>> Thanks. =A0I am wondering what CI stuff may break if we move to snapshot
>> dependency. =A0Any comments on that?
>>
>> Phil
>>>
>>> - J=F6rg
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

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