[
https://issues.apache.org/jira/browse/HADOOP-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214114#comment-15214114
]
Steve Loughran commented on HADOOP-12956:
-----------------------------------------
Has anyone spoken to the Log4J team about this?
Chris —that's an interesting q. about mixing. We'd need to make sure the SLF4J
to Log4j2 JAR was on the CP, and that log4j was off it. Would commons-logging
be able to feed in to log4j2 then? Or is a full move off it required? As that's
more expensive, especially as there are so many nested libraries which use what
has been the defacto Java logging API since the Avalon framework was written.
Would the log tuning servlets work? They are invaluable for debugging live
services.
we can still continue the move to SLF4J APIs, even for branch-2 code. it works
great as an API...it's the new back end which is the troublespot
> Inevitable Log4j2 migration via slf4j
> -------------------------------------
>
> Key: HADOOP-12956
> URL: https://issues.apache.org/jira/browse/HADOOP-12956
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Gopal V
>
> {{5 August 2015 --The Apache Logging Services™ Project Management Committee
> (PMC) has announced that the Log4j™ 1.x logging framework has reached its end
> of life (EOL) and is no longer officially supported.}}
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> A whole framework log4j2 upgrade has to be synchronized, partly for improved
> performance brought about by log4j2.
> https://logging.apache.org/log4j/2.x/manual/async.html#Performance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
