[ http://jira.qos.ch/browse/LBCLASSIC-121?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu edited comment on LBCLASSIC-121 at 11/25/09 9:42 PM: ---------------------------------------------------------------- The simplicity of the patch proposed by Hugues in LBCLASSIC-168 is quite attractive. I believe it would address the present issue as well. was (Author: noreply.ceki@qos.ch): The simplicity of the patch proposed by Hugues is quite attractive.
Make some of the Import-Package declarations in logback-classic OSGi bundle optional ------------------------------------------------------------------------------------
Key: LBCLASSIC-121 URL: http://jira.qos.ch/browse/LBCLASSIC-121 Project: logback-classic Issue Type: Improvement Components: Other Affects Versions: 0.9.15 Environment: OSGi Service Platform Release 4 Reporter: Pavol Juhos Assignee: Logback dev list Priority: Minor
It might be a good idea to mark some additional packages imported by logback-classis bundle as optional. Namely this applies to packages javax.servlet, javax.servlet.http, javax.management By importing package javax.servlet you are forcing the users to deploy Sevlet API bundle even in non-web application environment. The current <Import-Package> declaration in maven-bundle-plugin configuration: <Import-Package>sun.reflect;resolution:=optional, javax.jms;resolution:=optional, * </Import-Package> Suggested update: <Import-Package>sun.reflect;resolution:=optional, javax.jms;resolution:=optional, javax.servlet.*;resolution:=optional, javax.management;resolution:=optional, * </Import-Package> Feel free to close this as invalid if the above mentioned packages are _always_ required for correct operation of logback-classic.
-- 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