[
http://jira.qos.ch/browse/LBCLASSIC-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11525#action_11525
]
Ceki Gulcu commented on LBCLASSIC-184:
--------------------------------------
I have not yet applied Gunnar's changes but they look pretty reasonable.
However, my original question about reproducing such errors remains valid. What
in Orbit's repackaging procedure made the cyclic dependencies in logback to
surface? As mentioned previously, integration tests done using Felix pass just
fine. Would using Equinox yield different results? As you can imagine, I am
trying to anticipate future problems of the same kind.
> 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
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev
