[logback-dev] [JIRA] Created: (LBACCESS-16) Fix Import-Package declarations in logback-access bundle manifest

Christian Brensing (JIRA) noreply-jira at qos.ch
Wed Oct 20 15:51:51 CEST 2010

Fix Import-Package declarations in logback-access bundle manifest

                 Key: LBACCESS-16
                 URL: http://jira.qos.ch/browse/LBACCESS-16
             Project: logback-access
          Issue Type: Bug
            Reporter: Christian Brensing
            Assignee: Logback dev list
            Priority: Trivial

There are two minor issues that prevent the use of the LOGBack-Access bundle in an OSGi environment:

1. The bundle manifest for LOGBack-Access needs an similiar update as reported in the LOGBack-Classic-Issues LBCLASSIC-108 and LBCLASSIC-131, otherwise the RollingFileAppender can not be used due to OSGi's classloader restriction.
2. All Import-Packages are mandatory, meaning that you need both Jetty 6.x, Jetty 7.x and Tomcat bundles, otherwise LOGBack-Access will not be resolved. Typically you can only satisfy one requirement (org.mortbay.jetty.* or org.eclipse.jetty.* if you're using Jetty 6.x or 7.x as the servlet container repespectively org.apache.catalina.* while using Tomcat). Making these Imports optional would facilitate the use of the LOGBack-Access bundle.

Please update the Maven-Bundle-Plugin-Configuration in the POM, so that
1. the Core-Packages ch.qos.logback.core.rolling and ch.qos.logback.core.rolling.helper will be declared as Import-Packages
2. Jetty- and Tomcat-Imports are optional

Suggested update:


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