Hi Anton, Have you noticed that SLF4J is licensed under an MIT license? Also, given that logback-classic natively implements the SLF4J API, client code usually only comes into contact with SLF4J. Does that go to alleviate your concerns about logback's license, namely LGPL? Anton Tagunov wrote:
Hello gentlemen,
I've been very happy to discover SLF4J. Log4j has long needed a rework. SLF4J is a fresh wind :)
It can blow Log4J out of the water. If it goes MIT me thinks.
Ceki> Do we want Big Iron (insert your least favorite IT company here) Ceki> to legally pirate an open source project, say logback?
As SLF4J gains popularity it will likely be perceived as same in kind to Log4J.
However Big Co-s will rather "pirate" the conveniently licensed alternative.
I don't see how Log4J can be replaced this way. IMO Logback needs MIT/ASL.
cheers, Anton
P.S. "cross-posting" to my blog :) http://atagunov.blogspot.com/2008/05/slf4j-beyond-log4j.html