On 12/21/05, Henri Gomez <[EMAIL PROTECTED]> wrote: > - Did we keep the current code (2.0.2 compatible) and have the > 'deprecated' warning on 3.0 or did we update code to 3.0 requested > methods, for example using PostMethod params instead of setHttp11.
The former. I'd vote -1 for larger changes in the current project stage. We can check such modifications in as soon as 2.0.1 is out. However, being a maintenance release, it is really questionable whether loosing downwards compatibility isn't even reserved for the trunk? Jochen -- Often it does seem a pity that Noah and his party did not miss the boat. (Mark Twain)
