[ http://jira.qos.ch/browse/LBCLASSIC-184?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-184: -------------------------------------- Thank you for getting back to me with this info. I was wondering if the separation of logback-classic.jar into two distinct bundles was something you needed to do naturally in your environment or was it a step you imagined in order to provide a recipe as I asked you.
Remove Cyclic Dependencies between Classic, SLF4J API and SLF4J Impl --------------------------------------------------------------------
Key: LBCLASSIC-184 URL: http://jira.qos.ch/browse/LBCLASSIC-184 Project: logback-classic Issue Type: Task Components: Other Affects Versions: 0.9.18 Reporter: Gunnar Wagenknecht Assignee: Ceki Gulcu Attachments: context-selector.patch, mdc-move.patch
When working with Logback as OSGi bundles I found some issues regarding cyclic dependencies. Basically, code in "org.slf4j.impl" depends on "org.slf4j.api" as well as Logback classic. This is fine. However, code in Logback classic also depends on "org.slf4j.impl". This introduces a cycle.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira