[ http://jira.qos.ch/browse/LBCLASSIC-184?page=com.atlassian.jira.plugin.syste... ] Hugues Malphettes commented on LBCLASSIC-184: --------------------------------------------- Hi Ceki, Regarding the automated testing question: sorry we did not answer it. This issue appears only when we package logback the way Gunnar wants to do it for Eclipse Orbit: As the automated test are run with the logback-classic bundle containing both the org.slf4j.impl and the rest of logback-classic we don't see the issue: the circular dependency between packages is obviously not a problem inside when it is all inside the same bundle. Once we run the automated test with the orbit type of packaging proposed, felix (or equinox) will most likely complain and the test will fail. Does this answer your question? Hugues PS: I wish we could all use the exact same packaging.
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