[logback-user] Why LGPL instead of Apache License?
listid at qos.ch
Wed Dec 27 21:23:41 CET 2006
The LGPL was chosen for a number of reasons. First, it is a relatively
permissive license for those wishing to use logback as a logging
library. Second, those who wish to extend logback can do so as long as
they publish the results under the LGPL, a condition which I find
quite reasonable. Third, the LGPL help to differentiate between log4j
and logback as projects.
Moreover, given that logback is intended to be used behind the SLF4J
API, client code does not come in direct contact with logback
code. SLF4J is licensed under and MIT/X11 type of license. Thus, even
organizations such the ASF which do not permit the use of LGPL
licensed libraries, can use logback through SLF4J.
I hope this answers the question,
At 02:16 AM 12/27/2006, you wrote:
>Log4J employs the Apache License and wound up being the inspiration for the
>entire Logging Project at the ASF, why was the LGPL chosen as the license to
>employ for Logback?
Logback: The reliable, generic, fast and flexible logging framework for Java.
More information about the Logback-user