db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4120) derbyclient.jar is not a complete OSGi bundle
Date Tue, 27 May 2014 13:28:02 GMT

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

Rick Hillegas commented on DERBY-4120:
--------------------------------------

Charlie, I don't mean to send you on a wild goose chase here. What we're looking for is a
change to the Derby build scripts which will produce the standard jar files with the enough
OSGi metadata in the manifests to fix this problem. Maybe that's not possible. Aggregating
all of the jars into a single super jar ball won't be a solution which we can use in a Derby
release. Thanks.

> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message