You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Richard N. Hillegas (Jira)" <ji...@apache.org> on 2019/10/18 13:36:00 UTC

[jira] [Assigned] (DERBY-7056) Make Derby modules usable by OSGi-aware applications

     [ https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard N. Hillegas reassigned DERBY-7056:
------------------------------------------

    Assignee: Richard N. Hillegas

> Make Derby modules usable by OSGi-aware applications
> ----------------------------------------------------
>
>                 Key: DERBY-7056
>                 URL: https://issues.apache.org/jira/browse/DERBY-7056
>             Project: Derby
>          Issue Type: Task
>          Components: Build tools
>    Affects Versions: 10.15.1.3
>            Reporter: Richard N. Hillegas
>            Assignee: Richard N. Hillegas
>            Priority: Major
>
> OSGi R7 introduced support for JPMS modules in 2018 according to https://blog.osgi.org/2018/02/osgi-r7-highlights-java-9-support.html. This includes additional information which goes into jar file manifests. Support for this OSGi information was requested by an email thread on the user list: http://apache-database.10148.n7.nabble.com/OSGi-manifest-headers-td150560.html. We need advice from OSGi experts on how to make Derby modules usable by OSGi-aware applications. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)