this thread has gotten a bit out of hand now... I personally trust the HttpClient team to make the right decisions about the future of the code, and I even agree with the wording of the 2.1 release plan. "Breaking 2.0 API compatibility where absolutely unavoidable" is acceptable, as long as that sentence cannot interpreted as a free ticket to change the API all over the place.
Now, what started this discussion was just me pointing out that you removed a technically non-deprecated method. Your response sounded a bit offensive, implying that we're doing something weird by using CVS HEAD of HttpClient (which is totally normal at Jakarta). And your comment about API compatibility sounded like you don't care very much about preserving compatibility.
There is a *huge* difference between "we should make all possible efforts to keep API compatibility" (Michael) and "we will no longer be able to provide API compatibility" (Oleg). And the difference might not even be technical ;-)
Cheers, -chris
-- Christopher Lenz /=/ cmlenz at gmx.de
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
