[
https://issues.apache.org/jira/browse/HBASE-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894647#action_12894647
]
Lars Francke commented on HBASE-2608:
-------------------------------------
I'll finish up my other small issues and then take a stab at this by converting
the necessary config files and check out the web frontend.
When we have the config files in place everyone can transparently decide if he
wants to use commons-logging API (which should ideally phased out) or SLF4j. It
doesn't make a difference because the CL jar gets replaced by a wrapper that
forwards all calls to SLF4J anyway. This should make it very easy for everyone
to adapt if you decide to go this way.
> Switch to SLF4J
> ---------------
>
> Key: HBASE-2608
> URL: https://issues.apache.org/jira/browse/HBASE-2608
> Project: HBase
> Issue Type: Improvement
> Reporter: Benoit Sigoure
>
> There are 2 compelling reasons to switch from log4j to slf4j:
> * HBase provides a client library that is going to be embedded in another
> application. Using SLF4J lets the application chose whatever logging library
> it wants instead of imposing log4j.
> * When using SLF4J, we should use logback by default as it is basically a
> better, faster, stronger log4j. Same author, new design / new code. See
> http://logback.qos.ch/reasonsToSwitch.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
