[logback-user] Why LGPL instead of Apache License?

[cowwoc]

If my application is written against slf4j but I plug in logback at runtime
as the logging implementation doesn't this somehow imply that my application
is linking against logback and as such the LGPL applies?

Gili


Ralph Goers wrote:
> 
> 
> 
> cowwoc wrote:
>> Ceki,
>>
>> What is the legal implication of using Logback through slf4j? Does this
>> limit our obligations to slf4j's MIT license or does any aspect of
>> logback's
>> LGPL license pass through?
>>
>> Thank you,
>> Gili
>>
>>   
> Pass through to what? Any application that uses SLF4J is not a 
> derivative of Logback and isn't impacted by Logback's use of LGPL. OTOH, 
> if you write your own Logback components those would be derivative works 
> and would be impacted.
> 
> Ralph
> _______________________________________________
> Logback-user mailing list
> Logback-user at qos.ch
> http://qos.ch/mailman/listinfo/logback-user
> 
> 

-- 
View this message in context: http://www.nabble.com/Why-LGPL-instead-of-Apache-License--tp8058617p19119217.html
Sent from the Logback User mailing list archive at Nabble.com.