[
https://issues.apache.org/jira/browse/HADOOP-14624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222049#comment-16222049
]
Steve Loughran commented on HADOOP-14624:
-----------------------------------------
One concern of mine here is: what will a move to Log4J 2 do here? I think
moving to SLF4J as the arg is probably step 1, and it needs to be adopted
across the codebase, ready for that. So this change here is only part of a
sequence, but its critical first step.
Once this patch is in we should run through all classes which use it (13, none
in production) and move them on to SLF4J, Or, we do that as part of this patch
for a single migration & cut the old API out entirely
> 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: [email protected]
For additional commands, e-mail: [email protected]
