> However, I am leaning toward the compromise that is being proposed. > Remy, are you willing to allow the solution where log4j would be > required to compile but not to deploy, using stdout/err as normal, > or log4j if configured to do so? It would allow others to use log4j > if necessary, while keeping httpclient free of runtime dependencies. Ok if log4j isn't a runtime dependency. I think it would be useful to be able to fully disable logging (and rely on the interceptors), for example by adding a "if (logger != null)" or something like it around the logging calls. Remy
- RE: [httpclient] [VOTE] HTTP client 1.0 release Waldhoff, Rodney
- Re: [httpclient] [VOTE] HTTP client 1.0 release Vincent Massol
- Re: [httpclient] [VOTE] HTTP client 1.0 release Remy Maucherat
- RE: [httpclient] [VOTE] HTTP client 1.0 release Waldhoff, Rodney
- Re: [httpclient] [VOTE] HTTP client 1.0 release Remy Maucherat
- RE: [httpclient] [VOTE] HTTP client 1.0 release Waldhoff, Rodney
- Re: [httpclient] [VOTE] HTTP client 1.0 release Remy Maucherat
- RE: [httpclient] [VOTE] HTTP client 1.0 release Waldhoff, Rodney
- Re: [httpclient] [VOTE] HTTP client 1.0 release Vincent Massol
- Re: [httpclient] [VOTE] HTTP client 1.0 release Scott Sanders
- RE: [httpclient] [VOTE] HTTP client 1.0 release Remy Maucherat
- RE: [httpclient] [VOTE] HTTP client 1.0 release Waldhoff, Rodney
- Re: [httpclient] [VOTE] HTTP client 1.0 release Scott Sanders