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 12:41:02 GMT

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

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

None of the Derby committers are experts on OSGi. If someone can supply a patch and verify
that it works in OSGi environments, then one of the committers can verify that it doesn't
break our regression tests and check it in. If this is done in the next two weeks, then the
patch will make its way into the upcoming 10.11 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