You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/17 21:09:00 UTC
[jira] [Commented] (QPID-7372) [Java Broker] Remove hard dependency
on logback from broker-core
[ https://issues.apache.org/jira/browse/QPID-7372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654187#comment-16654187 ]
ASF GitHub Bot commented on QPID-7372:
--------------------------------------
Github user nitin1706 commented on the issue:
https://github.com/apache/qpid-broker-j/pull/13
Please update the version of dependency com.sleepycat:je::7.4.5 as the dependency is not available.
> [Java Broker] Remove hard dependency on logback from broker-core
> ----------------------------------------------------------------
>
> Key: QPID-7372
> URL: https://issues.apache.org/jira/browse/QPID-7372
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Priority: Major
> Fix For: qpid-java-6.1
>
>
> Currently the SystemConfig class has a hard dependency on LogBack, and forces instantiation / resetting the logback config.
> To allow for easier embedding of the broker we can move this instantiation out of the core model and into the code use to bootstrap the broker instance. We can also move the logback dependent model objects into a separate plugin. In this way the System Config (and child Broker) will simply use whatever has been set up for them in slf4j and an embedder of the broker could choose to use a different logging provider or supply a logback configuration which is not managed by the broker itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org