[
https://issues.apache.org/jira/browse/DERBY-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768542#action_12768542
]
Bryan Pendleton commented on DERBY-4120:
----------------------------------------
Where do I go to learn more about Export-Package and what it should contain?
I did a bit of poking about in the 10.5.3.0 distribution of Derby, and I see:
- derby.jar's Manifest.mf contains the following Export-Package information:
Export-Package: org.apache.derby.authentication,org.apache.derby.datab
ase,org.apache.derby.io,org.apache.derby.jdbc,org.apache.derby.vti
- none of the other Derby jar files (derbyclient.jar, derbytools.jar,
derbynet.jar, derbyrun.jar)
seem to contain Export-Package lines
So I guess my questions are:
1) Should we add Export-Package to *all* the Derby jar files? Or just
derbyclient.jar?
2) What value should it contain? Is it the same for each Derby jar file? Or
should it
have a different value in derbyclient.jar than it does in derby.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
>
> 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.
