qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomas Klimavicius (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7747) Logging: Depend only on slf4j and remove logback dependencies
Date Mon, 17 Apr 2017 13:42:41 GMT

    [ https://issues.apache.org/jira/browse/QPID-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971069#comment-15971069

Tomas Klimavicius commented on QPID-7747:

I'm referring to qpid-broker 6.1.2, the latest version i found in maven central. I did not
look over the code only Broker.class and it has dependencies on logback. And this is line
102 from Broker.class - 
ch.qos.logback.classic.Logger logger = (ch.qos.logback.classic.Logger)LoggerFactory.getLogger("ROOT");

> Logging: Depend only on slf4j and remove logback dependencies
> -------------------------------------------------------------
>                 Key: QPID-7747
>                 URL: https://issues.apache.org/jira/browse/QPID-7747
>             Project: Qpid
>          Issue Type: Improvement
>            Reporter: Tomas Klimavicius
> Qpid is depending on logback as it's log implementation, but this makes it horrible to
use inside projects that already use log4j or slf4j-jdk14.
> It would be much easier for users if the source code would only depened on slf4j. Now
if we exclude logback and expect qpid to use our provided logger the code does not compile
since qpid actually depends on logback - 
> ch.qos.logback.classic.Logger logger = (ch.qos.logback.classic.Logger)LoggerFactory.getLogger("ROOT");
> And if you use something else you get a class cast exception. 
> Also slf4j complains on every startup when you have multiple implementations in your

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message