[
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:
http://www.javaworld.com/javaworld/jw-03-2008/jw-03-osgi1.html?page=3
This article also says that importing must be done correctly:
http://www.osgi.org/blog/2007/04/importance-of-exporting-nd-importing.html
This article presents the Export-Package information from the Eclipse POV:
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html
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: 10.4.2.0
> 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.
