[
https://issues.apache.org/jira/browse/OOZIE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616702#comment-13616702
]
Robert Kanter commented on OOZIE-1287:
--------------------------------------
I'm not an expert on how slf4j or log4j work, but in OOZIE-1004, Alejandro
posted this comment:
{quote}
excluding the slf4j binding for log4j and log4j JARs.
Including slf4j api and the simple binding JARs.
slf4j does not allow you to have 2 bindings in the classpath, only one. Using
the simple one, thus no need for log4j JAR either.
{quote}
So, it sounds like he deliberately meant to leave out log4j. Though if slf4j
is "complaining and [not?] really outputting anything", then perhaps that's not
correct and it should be fixed.
> slf4j binding is required for running oozie client starting from hadoop
> 2.0.4-alpha
> -----------------------------------------------------------------------------------
>
> Key: OOZIE-1287
> URL: https://issues.apache.org/jira/browse/OOZIE-1287
> Project: Oozie
> Issue Type: Improvement
> Components: client
> Affects Versions: 3.3.1
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
>
> With Hadoop 2.0.4-alpha it is now now a requirement to have slf4j available
> for the oozie client to run (because of the hadoop-auth requiring it).
> I think it would not be a problem to include it even before Oozie migrates to
> Hadoop 2.0.4-alpha.
> Please let me know if I can submit a patch
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
