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] [Updated] (QPID-7747) Logging: Depend only on slf4j and remove logback dependencies
Date Mon, 17 Apr 2017 06:30:42 GMT

     [ https://issues.apache.org/jira/browse/QPID-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tomas Klimavicius updated QPID-7747:
------------------------------------
    Description: 
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 dependency qpid does not compile since it has code like this - 
ch.qos.logback.classic.Logger logger = (ch.qos.logback.classic.Logger)LoggerFactory.getLogger("ROOT");
It just must have logback. And if you use something else you get a class cast exception. 
Also slf4j will complain on every startup when you have multiple implementations in your classpath

  was:
Qpid is depending on logback as it's log implementation, but this makes it horrible to use
inside your projects where you 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 dependency qpid does not compile since it has code like this - 
ch.qos.logback.classic.Logger logger = (ch.qos.logback.classic.Logger)LoggerFactory.getLogger("ROOT");
It just must have logback. And if you use something else you get a class cast exception. 
Also slf4j will complain on every startup when you have multiple implementations in your classpath


> 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 dependency qpid does not compile since it has code like this - 
> ch.qos.logback.classic.Logger logger = (ch.qos.logback.classic.Logger)LoggerFactory.getLogger("ROOT");
> It just must have logback. And if you use something else you get a class cast exception.

> Also slf4j will complain 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


Mime
View raw message