Some input for you guys: in Aperture we have been using SLF4J (.org) for
a while now, after an intensive debate on the pros and cons of various
frameworks. See this archived mail thread:
http://sourceforge.net/mailarchive/forum.php?thread_name=45D9CF4A.3060707%40aduna-software.com&forum_name=aperture-devel
Summarized, we're using SLF4J because:
- It's only a facade API to program against, the developer that is
integrating Aperture can still determine which logging implementation is
used, by including the corresponding SLF4J driver jar file for that
logger in the classpath. As far as I can see, there is a driver for
every commonly used logger.
- There are serious classloading issues with java.util.logging (and
apparently also with Apache Commons Logging) that may make forwarding
calls to it to another logger effectively impossible in some scenarios.
For example, when Tika were to use java.util.logging and a user would
install two webapps containing Tika code, the log files of the two
webapps may get screwed up: one log file would contain messages of both
apps, the other would remain empty. This problem has happened to us in a
production system, so for us it's not a theoretical issue :)
I have had zero issues and complaints after the switch, so I guess it's
doing its job perfectly fine.
Regards,
Chris
--
