[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959985#comment-16959985
]
Mark Raynsford commented on DERBY-7056:
---------------------------------------
Ok, so as of this commit:
https://github.com/io7m/derby/commit/aba35f7518160fab44bd215b5d7f034ff4a14759
... we have a set of OSGi bundles that resolve correctly, and the locales use
derbyshared as the fragment host. I do, however, see the attached exception
when I shut down the OSGi framework. I suspect that the existing
BundleActivator didn't survive the JDK 9 modularization.
[^derby.txt]
> 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
> Attachments: derby.txt
>
>
> 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)
