[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956278#comment-16956278
]
Mark Raynsford commented on DERBY-7056:
---------------------------------------
For reference, I'm working on this fork: https://github.com/io7m/derby
[~laeubi] I'm currently slightly stuck with regards to handling the locale
jars. As of commit f09672295702cd4f0567fdf868149c8328f67c95, all of the created
jars (minus the derbyrun.jar and derby.war) have full OSGi metadata and
versioned package exports taken from the existing module descriptors. The
problem is that it's not clear to me if the locale jars can be made into
fragments because that would imply, in the current Derby setup, multiple
fragment hosts. I noticed an odd "Dynamic-Import: *" declaration in the old
OSGi manifest that makes me wonder if that's how locales were being handled
last time. Is there something better we can do?
> 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
> 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)
