You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2017/04/06 13:12:41 UTC
[jira] [Resolved] (QPID-7733) Misplaced
ch.qos.logback.classic.spi.Configurator services file prevents use of
logback in the Broker without the Qpid logging-logback module
[ https://issues.apache.org/jira/browse/QPID-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall resolved QPID-7733.
------------------------------
Resolution: Fixed
> Misplaced ch.qos.logback.classic.spi.Configurator services file prevents use of logback in the Broker without the Qpid logging-logback module
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7733
> URL: https://issues.apache.org/jira/browse/QPID-7733
> Project: Qpid
> Issue Type: Bug
> Affects Versions: qpid-java-6.1
> Reporter: Keith Wall
> Priority: Minor
> Fix For: qpid-java-broker-7.0.0, qpid-java-6.1.3
>
>
> The services file {{ch.qos.logback.classic.spi.Configurator}} still exists in the broker-core model. This references class {{org.apache.qpid.server.logging.logback.NoopConfigurator}} which was moved by QPID-7372 to the logging-logback module.
> The effect of this defect if a user wishes to embed the Broker *without* the Qpid's logging-logback module but *with* logback, this defect prevent them doing so. Logback tries to fails when it fails to load {{org.apache.qpid.server.logging.logback.NoopConfigurator}}.
>
--
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