Personally I think one should not replace a release with a new version
without changing its name. This causes confusion. So at least call it
RC2-build2 or something like that.
To ensure this does not happen again in the future, should we include a
check in the build.xml for the JavaC version
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24081.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Non-binding +1 to both suggestions.
Thanks
-Vincent
-Original Message-
From: Ortwin Glück [mailto:[EMAIL PROTECTED]
Sent: 30 October 2003 09:13
To: Commons HttpClient Project
Subject: Re: cactus-13-1.5-rc and commons-httpclient-2.0-rc2.jar works
on
jdk1.4 and above only?
Personally I think one should not replace a release with a new version
without changing its name. This causes confusion. So at least call it
RC2-build2 or something like that.
It's very common in such cases to append an 'a' to the version. So I
suggest you name it -rc2a.
Regards,
Ingo
Hi,
I'm using the nightly builds version of HttpClient and I have noticed that, when
a timeout occurs, neither ConnectTimeoutException nor IOTimeoutException are
ever thrown.
Instead, HttpConnection.ConnectionTimeoutException and
java.net.SocketTimeoutException are thrown in their place.
Is
Fabio,
HttpConnection.ConnectionTimeoutException should have been replaced with
ConnectTimeoutException. It's my oversight, for which I'll provide a
fix. IOTimeoutException usually is a wrapper for
java.io.InterruptedIOException. I guess the name does not adequately
reflect the nature of this
