[
https://issues.apache.org/jira/browse/OOZIE-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598440#comment-16598440
]
Andras Piros edited comment on OOZIE-3136 at 8/31/18 8:44 AM:
--------------------------------------------------------------
Hi [~bugg_tb],
we're targeting to resolve this issue in the next couple of weeks.
One who wants to get this resolved sooner needs to address following other
JIRAs:
* OOZIE-3135
* OOZIE-3137
was (Author: andras.piros):
Hi [~bugg_tb],
we're targeting to resolve this issue in the next couple of weeks.
The one who wants to get this resolved sooner needs to address following other
JIRAs:
* OOZIE-3135
* OOZIE-3137
> Upgrade from Log4j 1.x to 2.x
> -----------------------------
>
> Key: OOZIE-3136
> URL: https://issues.apache.org/jira/browse/OOZIE-3136
> Project: Oozie
> Issue Type: Improvement
> 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)
