Switch to SLF4J (from MinLog)

[GoogleCodeExporter]

SLF4J is preferrable MinLog for a variety of reasons, mostly around 
configurabliity, industry acceptance and adaptability. If you really want your 
logs consumed by someone, especially in a clustered environment, SLF4J is the 
best way to go.

From the groups: https://groups.google.com/forum/#!topic/kryo-users/-M--TGWfr7g

SLF4J is here:  http://slf4j.org

Original issue reported on code.google.com by m...@thebishops.org on 3 Jul 2013 at 7:29

[GoogleCodeExporter]

I second this. I am working on a bigger open-source framework in the moment and 
we want to use Kryo to make Ehcache-disk-caching more efficient but the logging 
choice of Kryo is still a major argument since all other dependencies as well 
as our framework rely on SLF4J. If you could change to SLF4J, this would be a 
major improvement. You could still offer MinLog as a possible configuration of 
SLF4J.

Thanks for the great work!

Original comment by rafael....@gmail.com on 11 Jul 2013 at 6:40

[GoogleCodeExporter]

MinLog can easily hand off the log messages to SLF4J, or any other logging 
library. The code to do so is literally a couple lines.

Original comment by nathan.s...@gmail.com on 5 Aug 2013 at 12:20

• Changed state: WontFix

[GoogleCodeExporter]

@Nate: Just to be clear. You mean something like providing a customized logger 
using minlog's setLogger API:
  Log.setLogger(new MyLogger()); 

where MyLogger hands off to SLF4J or anything else. Right?

Original comment by romixlev on 5 Aug 2013 at 1:21

[GoogleCodeExporter]

Yes, example here:
https://code.google.com/p/minlog/#Output_customization

Original comment by nathan.s...@gmail.com on 5 Aug 2013 at 1:22