You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2014/11/11 23:59:35 UTC
[jira] [Resolved] (MAVIBOT-36) Runtime dependencies on slf4j-log4j
and log4j cause conflicts
[ https://issues.apache.org/jira/browse/MAVIBOT-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved MAVIBOT-36.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0-M6
Fixed with http://svn.apache.org/r1638516
> Runtime dependencies on slf4j-log4j and log4j cause conflicts
> -------------------------------------------------------------
>
> Key: MAVIBOT-36
> URL: https://issues.apache.org/jira/browse/MAVIBOT-36
> Project: Mavibot
> Issue Type: Bug
> Affects Versions: 1.0.0-M4
> Reporter: lucas theisen
> Assignee: Emmanuel Lecharny
> Priority: Minor
> Fix For: 1.0.0-M6
>
>
> The mavibot artifact has runtime dependencies on slf4j-log4j and log4j which causes conflicts if the project depending on mavibot uses different bindings for the slf4j-api. For example, if you use logback instead of log4j then you end up with 2 different packages trying to bind to the same api. The decision of which binding to use should be left up to the runtime application.
> Workaround: add exclusions to the dependency on mavibot.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)