Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Thu, 6 Mar 2014 22:37:45 +0000 (UTC)
From: "lucas theisen (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12699283.1394145422611.18914.1394145465778@arcas>
In-Reply-To: <JIRA.12699283.1394145422611@arcas>
References: <JIRA.12699283.1394145422611@arcas>
Subject: [jira] [Created] (MAVIBOT-36) Runtime dependencies on slf4j-log4j
 and log4j cause conflicts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

lucas theisen created MAVIBOT-36:
------------------------------------

             Summary: 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


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.2#6252)