[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996444#comment-16996444
]
Richard N. Hillegas commented on DERBY-7056:
--------------------------------------------
Thanks, Mark.
1) Yes, please separate version-controlled space from generated artifact space.
We try to be careful about that in the Derby build. How about into a
generated/bnd directory, parallel to the generated/java and generated/bin
directories?
2) Who is the licensing entity/contributor/project? We will need to include
this information in the NOTICE file which we generate at release time. I can
take care of that piece if you give me the information. It involves creating an
attribution file in tools/release/notices and wiring that file into the
<buildnotice> target of the top level build.xml script.
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, complete0.diff, derby.txt,
> patch-20191213.diff
>
>
> 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)
