You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/05 04:19:28 UTC
[jira] [Updated] (STORM-290) Exclude log4j and slf4j-log4j from
curator dependency.
[ https://issues.apache.org/jira/browse/STORM-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Kellogg updated STORM-290:
-------------------------------
Component/s: storm-core
> Exclude log4j and slf4j-log4j from curator dependency.
> ------------------------------------------------------
>
> Key: STORM-290
> URL: https://issues.apache.org/jira/browse/STORM-290
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 0.9.2-incubating
> Reporter: P. Taylor Goetz
> Assignee: P. Taylor Goetz
> Fix For: 0.9.2-incubating
>
>
> 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.3.4#6332)