[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996830#comment-16996830
]
Mark Raynsford edited comment on DERBY-7056 at 12/15/19 6:28 PM:
-----------------------------------------------------------------
??Who wrote the code in the bnd jar file? If we are going to include this jar
in a Derby distribution, then the Apache 2.0 license requires that we give
credit to its author(s).??
The jar is the "bnd" tool, and it was written by a large group of people. I
think the primary author is [~pkriens], but I know [~bjhargrave] and
[~rotty3000] have also worked on it. It's a standard tool used indirectly by
any project that uses the either the maven-bundle-plugin or bnd-maven-plugin
(which seems to be almost every Java project I see these days), or directly by
people using the Bndtools IDE plugin.
??Bear with me, I'm still not clear about the status of the bnd directory. Are
the following files source code which need to be included in the patch when it
is committed, or are they generated files???
The files in the bnd directory are source code and need to be included in the
patch when committed. I confused the issue originally by including entries in
the .gitignore file that weren't relevant to the patch. :P
??Finally, I am getting an error with this patch when I try to build the jar
files.??
I'll take a look at this. I've been building using:
{noformat}
$ ant clobber buildsource buildjars
{noformat}
... as per the documentation.
was (Author: io7m):
??Who wrote the code in the bnd jar file? If we are going to include this jar
in a Derby distribution, then the Apache 2.0 license requires that we give
credit to its author(s).??
The jar is the "bnd" tool, and it was written by a large group of people. I
think the primary author is Peter Kriens [~pkriens], but I know BJ Hargrave
[~bjhargrave] and Raymond Auge [~rotty3000] have also worked on it. It's a
standard tool used indirectly by any project that uses the either the
maven-bundle-plugin or bnd-maven-plugin (which seems to be almost every Java
project I see these days), or directly by people using the Bndtools IDE plugin.
??Bear with me, I'm still not clear about the status of the bnd directory. Are
the following files source code which need to be included in the patch when it
is committed, or are they generated files???
The files in the bnd directory are source code and need to be included in the
patch when committed. I confused the issue originally by including entries in
the .gitignore file that weren't relevant to the patch. :P
??Finally, I am getting an error with this patch when I try to build the jar
files.??
I'll take a look at this. I've been building using:
{noformat}
$ ant clobber buildsource buildjars
{noformat}
... as per the documentation.
> 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)
