Scott Eade wrote:
BUT: commons-http is not being maintained by anyone at present - it doesn't even appear on the commons components page and the last commit was 7 months ago.[x] Yes, delete the deprecated code and add a dependency on commons-http [ ] No, fix the deprecated code, and undeprecate it.
I use commons-http in my application so as to avoid the deprecation warning from BrowserDetector, but commons-http needs to be patched in order to do what I want (public access to the constants), but due to the low level of attention commons-http gets my patch was lost in the massive flow of traffic that is commons-dev:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=32393
commons-http is a really small component - I agree that it should be fixed and then released. If there is not enough interest in releasing it then I think it should be rolled it back into turbine.
My first reaction would be to roll-it-back. Depending on something that has a questionable communiy/backing is bit a good idea.
Stephen.
Scott
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
