[jira] Resolved: (DERBY-4120) derbyclient.jar is not a complete OSGi bundle

["Myrna van Lunteren (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren resolved DERBY-4120.
---------------------------------------

         Assignee: Bryan Pendleton  (was: Myrna van Lunteren)
    Fix Version/s: 10.5.3.1
       Resolution: Fixed

Committed backport to 10.5 with revision 963799.
Merge command was: svn merge -c 830545 https://svn.apache.org/repos/asf/db/derby/code/trunk

I confirmed that the appropriate entry is present in the META-INF/MANIFEST.MF file in derbyclient.jar.

> derbyclient.jar is not a complete OSGi bundle
> ---------------------------------------------
>
>                 Key: DERBY-4120
>                 URL: https://issues.apache.org/jira/browse/DERBY-4120
>             Project: Derby
>          Issue Type: Bug
>          Components: Eclipse Plug-in, Services
>    Affects Versions: 10.4.2.0
>         Environment: OSGi
>            Reporter: JJ Snyder
>            Assignee: Bryan Pendleton
>             Fix For: 10.5.3.1, 10.6.1.0
>
>         Attachments: addToManifest.diff
>
>
> The manifest in derbyclient.jar is incomplete for usage in OSGi.  There are no packages exported.  This appears to only be a problem in standalone equinox (outside of eclipse).  Note that I did not try other OSGi containers.
> The fix is relatively simple.  Adding the Export-Package manifest header should take care of the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.