[logback-dev] [JIRA] Resolved: (LBCLASSIC-184) Remove Cyclic Dependencies between Classic, SLF4J API and SLF4J Impl

Ceki Gulcu (JIRA) noreply-jira at qos.ch
Thu Mar 25 12:28:17 CET 2010


     [ http://jira.qos.ch/browse/LBCLASSIC-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu resolved LBCLASSIC-184.
----------------------------------

    Fix Version/s: 0.9.19
       Resolution: Fixed

This issue was fixed in 0.9.19. However, if for reason you observe other cyclic behavior please file a new report or re-open this one.

> 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
>            Priority: Critical
>             Fix For: 0.9.19
>
>         Attachments: context-selector.patch, mdc-move.patch, TEST-org.slf4j.test_osgi.BundleTest.txt
>
>
> 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

        


More information about the logback-dev mailing list