Hola,
>But more cooperation/integration testing would be nice. Does the James
>or tomcat group do a JDK1.3 compatibility check?
For tomcat, basically no. The releases have been compiled and tested
with JDK 1.4 for a while now, and that's what most of our users use, so
we haven't gotten complain
> > But more cooperation/integration testing would be nice. Does the James
> > or tomcat group do a JDK1.3 compatibility check?
> i've been wondering for a little while whether it'd be possible to use
> gump for extended compatibility tests.
I would certainly hope so. :-)
--- Noel
--
Dirk Verbeeck wrote:
> DBCP 1.1 was also compiled with JDK1.4 so I think we're safe for now.
> I don't follow the f(T) thing.
Example:
JDK 1.3 has: public synchronized StringBuffer append(Object obj)
JDK 1.4 adds: public synchronized StringBuffer append(StringBuffer sb)
The following code:
robert burrell donkin wrote:
i've been wondering for a little while whether it'd be possible to use
gump for extended compatibility tests.
That would be nice. Because of all these dependencies it is very hard
to test how existing/released components react on an upgrade of a
dependency.
For exam
On 14 Jun 2004, at 22:27, Dirk Verbeeck wrote:
But more cooperation/integration testing would be nice. Does the James
or tomcat group do a JDK1.3 compatibility check?
i've been wondering for a little while whether it'd be possible to use
gump for extended compatibility tests.
- robert
-
If DBCP is compiled with JDK 1.3 then some methods are commented out
because they are only in the JDBC3 spec (included in JDK1.4). So then
we need 2 releases.
To trigger the dbcp incompatibility I has to set the defaultReadOnly
property. The class with the JDK1.4 method call was loaded normally
I tested Pool 1.2 and it can be compiled with JDK 1.3.1_01.
So that one should be OK.
-- Dirk
Noel J. Bergman wrote:
DBCP 1.2.1 is a maintenance release to restore full JDK 1.3 compatibility.
[X] +1 Go for it!
Was there anything similar in Pool? And can we compile the release packages
with JDK 1.
Hi,
+1.
Yoav Shapira
Millennium Research Informatics
>-Original Message-
>From: Dirk Verbeeck [mailto:[EMAIL PROTECTED]
>Sent: Saturday, June 12, 2004 10:19 AM
>To: Jakarta Commons Developers List
>Subject: [VOTE][DBCP] Release commons-dbcp v1.2.1
>
>DBCP 1.2.1 is a maintenance release
> DBCP 1.2.1 is a maintenance release to restore full JDK 1.3 compatibility.
> [X] +1 Go for it!
Was there anything similar in Pool? And can we compile the release packages
with JDK 1.3?
--- Noel
-
To unsubscribe, e-ma
> DBCP 1.2.1 is a maintenance release to restore full JDK 1.3 compatibility.
>
> Cast your votes please:
>
> [X] +1 Go for it!
> [ ] -1 I found another issue
And I urge everyone to please COMPILE all releasables with
**
+1
- Original Message -
From: "Dirk Verbeeck" <[EMAIL PROTECTED]>
> DBCP 1.2.1 is a maintenance release to restore full JDK 1.3 compatibility.
>
> Details can be found here:
> http://cvs.apache.org/~dirkv/dbcp/release-notes-1.2.1.html
>
> CVS head tagged as DBCP_1_2_1
> Distribution can be
+1 from me of course
-- Dirk
Dirk Verbeeck wrote:
DBCP 1.2.1 is a maintenance release to restore full JDK 1.3 compatibility.
Details can be found here:
http://cvs.apache.org/~dirkv/dbcp/release-notes-1.2.1.html
CVS head tagged as DBCP_1_2_1
Distribution can be previewed here:
http://cvs.apache.org/
12 matches
Mail list logo
