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 14:22:02 GMT

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

Rick Hillegas commented on DERBY-4120:

That's a useful analysis, Christian. I agree that the factoring of the packages into jar files
is broken. I don't think we're going to refactor Derby in the 10.11 timeframe. We may be able
to fix this when we refactor Derby to take advantage of the Jigsaw work being done in Java
9. But that won't provide any near term relief for OSGi users. 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:
>         Environment: OSGi
>            Reporter: JJ Snyder
>            Assignee: Bryan Pendleton
>             Fix For:,
>         Attachments: addToManifest.diff, derby OSGI issue.jpg
> 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

View raw message