[
https://issues.apache.org/jira/browse/HDFS-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592927#comment-14592927
]
Sean Busbey commented on HDFS-6564:
-----------------------------------
You should include mention of how to get the same functionality. In this case,
they can retrieve the named logger via the logging framework of their choice
directly. Since the previous member was commons-logging object, that would be
done via {{LogFactory.getLog(CachePoolInfo.class)}} or
{{LogFactory.getLog("org.apache.hadoop.hdfs.protocol.CachePoolInfo")}}.
> Use slf4j instead of common-logging in hdfs-client
> --------------------------------------------------
>
> Key: HDFS-6564
> URL: https://issues.apache.org/jira/browse/HDFS-6564
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Haohui Mai
> Assignee: Rakesh R
> Attachments: HDFS-6564-01.patch, HDFS-6564-02.patch,
> HDFS-6564-03.patch
>
>
> hdfs-client should depends on slf4j instead of common-logging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
