[
https://issues.apache.org/jira/browse/HADOOP-15749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612006#comment-16612006
]
Steve Loughran commented on HADOOP-15749:
-----------------------------------------
yes, these should be culled. Maybe it'd be possible for some
checkstyle/findbugs check to reject refs to it from any production source.
> Unhandled Log4JLogger explicit reference breaks non-log4j users
> ---------------------------------------------------------------
>
> Key: HADOOP-15749
> URL: https://issues.apache.org/jira/browse/HADOOP-15749
> Project: Hadoop Common
> Issue Type: Bug
> Components: common
> Affects Versions: 3.1.1
> Reporter: Vitalii Diravka
> Priority: Major
>
> The aim of this Jira is the same as HADOOP-10288, but there are more places
> where the issue should be solved, for instance
> {{MetricsLoggerTask.makeMetricsLoggerAsync()}} is called from
> {{NameNode.initialize()}.
> Possible solution: the logic from HADOOP-10288 could be factored out to
> {{GenericsUtil}} and can be used where it is necessary.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
