Logging wars; was Re: svn commit: r711289

[Oleg Kalnichevski <ol...@apache.org>]

On Tue, 2008-11-04 at 11:16 -0500, Ryan McKinley wrote:
> I had hoped we could use SLF4J:
> https://issues.apache.org/jira/browse/DROIDS-9
> 
> but since commons http component already depends on commons logging,  
> perhaps it is best to stick with that...
> 
> 

Ryan

CL and SLF4J are not mutually exclusive. As far as I know SLF4J provides
a CL bridge which is (expected to be) fully binary compatible with the
official CL implementation. One can compile against CL and deploy with
SLF4J. This is one of the reasons why we decided to stick to CL for
HttpClient 4.0.

Oleg 

Re: Logging wars; was Re: svn commit: r711289

[Ryan McKinley <ry...@gmail.com>]

On Nov 4, 2008, at 12:05 PM, Oleg Kalnichevski wrote:

> On Tue, 2008-11-04 at 11:16 -0500, Ryan McKinley wrote:
>> I had hoped we could use SLF4J:
>> https://issues.apache.org/jira/browse/DROIDS-9
>>
>> but since commons http component already depends on commons logging,
>> perhaps it is best to stick with that...
>>
>>
>
> Ryan
>
> CL and SLF4J are not mutually exclusive. As far as I know SLF4J  
> provides
> a CL bridge which is (expected to be) fully binary compatible with the
> official CL implementation. One can compile against CL and deploy with
> SLF4J. This is one of the reasons why we decided to stick to CL for
> HttpClient 4.0.
>

yes, they have:
http://www.slf4j.org/legacy.html
you can install 'jcl-over-slf4j.jar' to use that

since HttpClient uses CL, we are stuck with CL in the classpath  
anyway, so i guess there is not much to worry about ;)

Commons logging it is...