commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Benedict <pbened...@apache.org>
Subject Re: [dbcp] 2.0 prep
Date Sun, 17 Oct 2010 16:10:46 GMT
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> wrote:
>> On 10/17/10 9:57 AM, Jörg 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.  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.
>>
>> Thanks.  I am wondering what CI stuff may break if we move to snapshot
>> dependency.  Any comments on that?
>>
>> Phil
>>>
>>> - Jörg
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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


Mime
View raw message