[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991016#comment-16991016
]
Richard N. Hillegas commented on DERBY-7056:
--------------------------------------------
Hey Mark,
Those patches don't apply for me. The following advice comes out on top when I
google for how to create an svn patch from git:
https://scribu.net/wordpress/svn-patches-from-git.html
If that's what you tried already, then we'll need to poke around some more.
Also, could you attach a description of the changes so that I know what I'm
looking at? Please assume that I know practically nothing about how to work
with OSGi. That will help me understand your patch. Thanks.
> 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)