[
http://jira.qos.ch/browse/LBCLASSIC-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11510#action_11510
]
Ceki Gulcu commented on LBCLASSIC-184:
--------------------------------------
Hello Gunnar,
Logback comes with OSGi-related tests that are supposed to catch such problems.
Under what circumstances did you observe the cycle? If possible, I would like
to reproduce the problem and incorporate it as a scenario into our tests.
> 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: Logback dev list
> 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
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://qos.ch/mailman/listinfo/logback-dev
