[
https://issues.apache.org/jira/browse/HBASE-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873325#action_12873325
]
stack commented on HBASE-2608:
------------------------------
SLF4J comes in because of AVRO?
There is a bit of folk knowledge built up around CL and log4j. We all know how
to mess with enabling and disabling log levels and in the UI there are tools to
enable/disable log levels. If we made the change, wouldn't this all be broke
or is the model such that the UI log level servlet can be made work w/ the new
regime, etc?
The classloading issue recently popped up messing with getting mockito running
in a minihbasecluster context.
Do you think this a priority Lars?
> 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.
