db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4120) derbyclient.jar is not a complete OSGi bundle
Date Thu, 22 Oct 2009 16:35:01 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768754#action_12768754

Bryan Pendleton commented on DERBY-4120:

A little bit of research on the web:

This article mentions both Export-Package and Import-Package:

This article also says that importing must be done correctly:

This article presents the Export-Package information from the Eclipse POV:

It seems like the simplest change would be to put the identical Export-Package
line into derbyclient.jar as is used for derby.jar.

I don't understand what this would *fix*, but I can at least prototype this and
verify that it doesn't *break* anything (that is revealed by the regression tests).

> 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:
>         Environment: OSGi
>            Reporter: JJ Snyder
>            Assignee: Bryan Pendleton
> 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.

View raw message