[
https://issues.apache.org/jira/browse/HADOOP-14624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226016#comment-16226016
]
Akira Ajisaka commented on HADOOP-14624:
----------------------------------------
I'm thinking
step1: moving logging APIs to slf4j
step2: replace slf4j -> log4j1 bridge with slf4j -> log4j2
so here is a step1 and there are many other jiras for step1. (HADOOP-14289,
MAPREDUCE-6946, YARN-6712, ...)
bq. we should run through all classes which use it (13, none in production) and
move them on to SLF4J
Yes, we should do this.
> Add GenericTestUtils.DelayAnswer that accept slf4j logger API
> -------------------------------------------------------------
>
> Key: HADOOP-14624
> URL: https://issues.apache.org/jira/browse/HADOOP-14624
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Wenxin He
> Assignee: Wenxin He
> Attachments: HADOOP-14624.001.patch, HADOOP-14624.002.patch
>
>
> Split from HADOOP-14539.
> Now GenericTestUtils.DelayAnswer only accepts commons-logging logger API. Now
> we are migrating the APIs to slf4j, slf4j logger API should be accepted as
> well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
