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 Wed, 19 Apr 2017 06:04:41 GMT

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

Tomas Klimavicius commented on QPID-7747:

Thanks [~alex.rufous], the example works. Since logback dependency is done by design for qpid-broker
then the ticket can be closed.
And maybe [~alex.rufous] can give an exmaple of how to disable secure only mechanisms as documented
in the programmatic approach? 

> 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
>         Attachments: embedded-broker-example.tar.gz
> 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