[
https://issues.apache.org/jira/browse/OOZIE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504447#comment-16504447
]
Andras Piros commented on OOZIE-3274:
-------------------------------------
[~bpgergo] can you please elaborate more on the motivation? I see that you try
to remove {{org.slf4j}} and replace it with {{org.apache.common.logging}}.
Why do we want to switch to Apache Commons Logging in the first place? Why do
we want to get rid of Slf4J? If you want to eliminate duplicate dependencies,
you can already do so.
Slf4J being rather a high-level logging API than an implementation itself, is
pluggable, and could be used [*across a variety of
implementations*|https://www.slf4j.org/legacy.html].
> Remove slf4j
> ------------
>
> Key: OOZIE-3274
> URL: https://issues.apache.org/jira/browse/OOZIE-3274
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Péter Gergő Barna
> Assignee: Péter Gergő Barna
> Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3274.rebased.patch
>
>
> Remove all slf4j jars from Oozie.
> I am not sure if Oozie works perfectly without slf4j jars, for me it seems
> that all kinds of hadoop2 jobs are working fine. Any comments are welcomed,
> I would appreciate a response from the community on this.
>
> I know about this issue, which introduced slf4j as a dependency, I am not
> sure if this is relevant any more.
> https://issues.apache.org/jira/browse/OOZIE-1004
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
