You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2017/04/17 10:02:42 UTC

[jira] [Commented] (QPID-7747) Logging: Depend only on slf4j and remove logback dependencies

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

Lorenz Quack commented on QPID-7747:
------------------------------------

What version of Qpid is this referring to?
We already did some work in this space in Qpid v6.1 and more on trunk.


> 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 classpath



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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