[logback-dev] [JIRA] Resolved: (LBCORE-101) OSGi manifest headers too restrictive

[Ceki Gulcu (JIRA)]

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

Ceki Gulcu resolved LBCORE-101.
-------------------------------

    Fix Version/s: 0.9.18
       Resolution: Fixed

David, many thanks for this report. Issue fixed in 

http://github.com/ceki/logback/commit/0334b5b0597eeb09a5319a00c69c1867a17b5b2f

> OSGi manifest headers too restrictive
> -------------------------------------
>
>                 Key: LBCORE-101
>                 URL: http://jira.qos.ch/browse/LBCORE-101
>             Project: logback-core
>          Issue Type: Bug
>    Affects Versions: 0.9.15
>            Reporter: david varnes
>            Assignee: Ceki Gulcu
>             Fix For: 0.9.18
>
>         Attachments: logback-core.osgi-manifest.patch
>
>
> This issue is very similar and could be addressed at the same time as LBCLASSIC-119, LBCLASSIC-121 & LBCLASSIC-131.
> The Import-Package definition for logback-core requires that the javax.* packages be available at runtime.
> The pom.xml file and my usage seem to indicate that they should be optional.
> Attached patch adds javax.* as 'optional' in addition to the exiting janino declaration.
> thanks !

-- 
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