[
https://issues.apache.org/jira/browse/HADOOP-16377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868037#comment-16868037
]
Steve Loughran commented on HADOOP-16377:
-----------------------------------------
OK, I'm really sorry, I wasn't clear enough. You don't need to change the order
of things, just when you add new stuff try and put them in the new areas.
Where things are out of order with existing classes we leave them alone,
because that's where a lot of the merge pain comes in. So a big slic e of the
new patch isn't needed. Like I said, sorry.
change to Filesystem LGTM
> Moving logging APIs over to slf4j
> ---------------------------------
>
> Key: HADOOP-16377
> URL: https://issues.apache.org/jira/browse/HADOOP-16377
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Wei-Chiu Chuang
> Assignee: Prabhu Joseph
> Priority: Major
> Attachments: HADOOP-16357-002.patch, HADOOP-16377-001.patch,
> HADOOP-16377-003.patch
>
>
> As of today, there are still 50 references to log4j1
> {code}
> $ grep -r "import org.apache.commons.logging.Log;" . |wc - l
> 50
> {code}
> To achieve the goal of HADOOP-12956/HADOOP-16206, we should invest time to
> move them to slf4j
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
