Github user rgodfrey commented on the issue:
https://github.com/apache/qpid-java/pull/1
Unfortunately it seems that logback changes its API frequently without
attempting to retain compatibility with its prior versions.
While this change (albeit enhanced with changes to the tests that are
required because of differences between 1.1.3 and 1.1.4) would work with 1.1.7,
switching to 1.1.10 (the current latest on the 1.1.x line) would fail because a
separate part of the logback API has been changed (in a way in which it would
have been easier for them to retain compatibility rather than break it... but
never mind).
Having a different release of Qpid for each release of LogBack seems an
unappealing solution, so I think we need to examine how we deal with this issue
in general.
If Qpid is being used only in tests, do you need to include the
logging-logback plugin at all? Would it not be better to configure logback
externally to Qpid, and simply omit the logback-logging plugin (and
configuration of broker/virtualhost loggers) from your testing configuration?
(this requires Qpid 6.1.x or later). Outside of the logging-logback plugin the
broker simply uses the slf4j api I believe.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
