[
https://issues.apache.org/jira/browse/HADOOP-18206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682084#comment-17682084
]
ASF GitHub Bot commented on HADOOP-18206:
-----------------------------------------
steveloughran commented on PR #5315:
URL: https://github.com/apache/hadoop/pull/5315#issuecomment-1408635376
so those production classes I am worrying about are already explicitly
requiring log4j on the CP? OK, that's not as bad as I feared...I was worrying
that the code was going from commons-logging wrappers of logj to raw log4j,
which is a problem
> Cleanup the commons-logging references in the code base
> -------------------------------------------------------
>
> Key: HADOOP-18206
> URL: https://issues.apache.org/jira/browse/HADOOP-18206
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
>
> Should always use slf4j
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
