[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956322#comment-16956322
]
Christoph Läubrich commented on DERBY-7056:
-------------------------------------------
In the plain jar, all locale jars where attached to the derby.jar, so I assumed
that in a OSGi- version all locale ones are fragments od the derby.jar host and
do not inlcude additional import/export headers, as fragemnts are handles as if
the where on the same classpath as the host. So to tell a little bit more it
would be good to konw: Is ther only one derby-osgi-jar (beside
war/run/fragments) or are there multiple ones?
> 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)
