[
https://issues.apache.org/jira/browse/OOZIE-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641930#comment-16641930
]
Peter Bacsko commented on OOZIE-3136:
-------------------------------------
HADOOP-12956 proposed a complete migration to Log4j2. I think we should do that
as well. It is certainly more complex, but cleaner.
Having both the adapter layer and the original log4j on the classpath can cause
strange issues. For example, an application wants to use the legacy log4j and
the classloader finds the adapter classes first and it will redirect all
logging calls to log4j2. Depending on the situation this might or might not be
what we want, but in general, having the same API in two different artifacts is
simply a pain and a perfect recipe for hard-to-debug problems.
> Upgrade from Log4j 1.x to 2.x
> -----------------------------
>
> Key: OOZIE-3136
> URL: https://issues.apache.org/jira/browse/OOZIE-3136
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Attila Sasvari
> Assignee: Julia Kinga Marton
> Priority: Major
>
> {{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
> We should upgrade from Log4j 1.x to 2.x . Perhaps we could use slf4j .
> Related tickets: MAPREDUCE-6983, HADOOP-12956, OOZIE-3135
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
