[
https://issues.apache.org/jira/browse/HADOOP-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419243#comment-15419243
]
Sean Busbey commented on HADOOP-13344:
--------------------------------------
{quote}
If there is a downstream project including hadoop-common (or any other
component), I say it's the responsibility of that project to exclude the slf4j
binding if they don't want it. I don't believe any changes to pom.xml are
necessary.
{quote}
disagree. Specifically, if folks are using the hadoop-client artifact(s) those
are expressly supposed to be a library for downstream users. SLF4j is pretty
clear on their guidance for libraries wrt including bindings. Just have the API
and let an end user decide if they need logging to go somewhere.
> Add option to exclude Hadoop's SLF4J binding
> --------------------------------------------
>
> Key: HADOOP-13344
> URL: https://issues.apache.org/jira/browse/HADOOP-13344
> Project: Hadoop Common
> Issue Type: New Feature
> Components: bin, scripts
> Affects Versions: 2.8.0, 2.7.2
> Reporter: Thomas Poepping
> Assignee: Thomas Poepping
> Labels: patch
> Attachments: HADOOP-13344.patch
>
>
> If another application that uses the Hadoop classpath brings in its own SLF4J
> binding for logging, and that jar is not the exact same as the one brought in
> by Hadoop, then there will be a conflict between logging jars between the two
> classpaths. This patch introduces an optional setting to remove Hadoop's
> SLF4J binding from the classpath, to get rid of this problem.
> This patch should be applied to 2.8.0, as bin/ and hadoop-config.sh structure
> has been changed in 3.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
