db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4120) derbyclient.jar is not a complete OSGi bundle
Date Fri, 23 Oct 2009 09:08:59 GMT

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

Knut Anders Hatlen commented on DERBY-4120:

I see that the list of exported packages in derby.jar is close to, but not exactly the same
as the list of packages in the published API (http://db.apache.org/derby/javadoc/publishedapi/jdbc4/).
Based on what you have found till now, do you think they should be identical?

Exporting org.apache.derby.jdbc in derbyclient.jar sounds like a fine, focused fix to the
problem reported here, so +1 from me. (But all I know about this is what I read from the links
you provided, so I'm definitely not an authority.)

> 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