[
https://issues.apache.org/jira/browse/STORM-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976975#comment-13976975
]
ASF GitHub Bot commented on STORM-290:
--------------------------------------
GitHub user ptgoetz opened a pull request:
https://github.com/apache/incubator-storm/pull/81
STORM-290: Exclude log4j and slf4j-log4j12 from curator dependency
This fixes a log binding conflict that occurs when using storm-core as a
project dependency.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptgoetz/incubator-storm zk-log4j-excludes
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-storm/pull/81.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #81
----
commit f6daf072fd644247090f44e6d054a934974e901a
Author: P. Taylor Goetz <[email protected]>
Date: 2014-04-22T16:10:35Z
exclude log4j and slf4j-log4j12 from curator dependency
----
> Exclude log4j and slf4j-log4j from curator dependency.
> ------------------------------------------------------
>
> Key: STORM-290
> URL: https://issues.apache.org/jira/browse/STORM-290
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Affects Versions: 0.9.2-incubating
> Reporter: P. Taylor Goetz
> Assignee: P. Taylor Goetz
>
> The log4j and slf4j dependencies from curator/zookeeper sneak onto the class
> path as transient dependencies when storm-core is included as a project
> dependency. This causes an illegal argument exception due to multiple log
> bindings on the class path.
> The solution is to exclude the log4j and slf4j dependencies in the storm-core
> pom rather than the parent pom.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
