[ https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991512#comment-16991512 ]
Mark Raynsford commented on DERBY-7056: --------------------------------------- Hm. Yes, that scribu.net guide was the one I followed. I'll open a PR so we at least have that in place. The commit messages do go into some detail as to what changed, but I'll write up something more complete. > 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: 0001-Initial-production-of-OSGi-manifests.patch, > 0002-Initial-production-of-OSGi-manifests-for-locales.patch, > 0003-Produce-working-locales-fragments-and-refactor.patch, > 0004-Reintroduce-Class-Path-attributes.patch, > 0005-Clear-BundleActivator.patch, 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)