Gary Gregory wrote:
> IMO:
>
> DBCP 1.4 for JDBC 4 (JDK 1.6)
> => Bump it to 2.0.
>
> DBCP 1.3 for JDBC 3 (JDK 1.4-1.5)
> => Stays as is.
As Phil said, it was discussed at release time. The main reason to go with
this version scheme is, that you can simply exchange the 1.3.x with 1.4.x
versio
On 4/27/11 8:30 AM, Gary Gregory wrote:
> IMO:
>
> DBCP 1.4 for JDBC 4 (JDK 1.6)
> => Bump it to 2.0.
>
> DBCP 1.3 for JDBC 3 (JDK 1.4-1.5)
> => Stays as is.
This is essentially the plan that we agreed to a year ago. The only
difference in what you have above is that we will likely cut at
least an
IMO:
DBCP 1.4 for JDBC 4 (JDK 1.6)
=> Bump it to 2.0.
DBCP 1.3 for JDBC 3 (JDK 1.4-1.5)
=> Stays as is.
Gary
On Wed, Apr 27, 2011 at 9:05 AM, sebb wrote:
> All Commons components other than DBCP have at most one current
> version per major release (e.g. NET has 1.4.1 and 2.2).
>
> DBCP uses a
On 4/27/11 6:29 AM, Jörg Schaible wrote:
> sebb wrote:
>
>> All Commons components other than DBCP have at most one current
>> version per major release (e.g. NET has 1.4.1 and 2.2).
>>
>> DBCP uses a different versioning scheme from all other components:
>>
>> DBCP 1.4 for JDBC 4 (JDK 1.6)
>> DBCP
sebb wrote:
> All Commons components other than DBCP have at most one current
> version per major release (e.g. NET has 1.4.1 and 2.2).
>
> DBCP uses a different versioning scheme from all other components:
>
> DBCP 1.4 for JDBC 4 (JDK 1.6)
> DBCP 1.3 for JDBC 3 (JDK 1.4-1.5)
>
> This is rather
All Commons components other than DBCP have at most one current
version per major release (e.g. NET has 1.4.1 and 2.2).
DBCP uses a different versioning scheme from all other components:
DBCP 1.4 for JDBC 4 (JDK 1.6)
DBCP 1.3 for JDBC 3 (JDK 1.4-1.5)
This is rather confusing.
Seems to me it wou
