[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996808#comment-16996808
]
Richard N. Hillegas commented on DERBY-7056:
--------------------------------------------
Hey Mark,
Sorry for not being clear. 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).
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?
{noformat}
bnd/derby.bnd
bnd/derbyLocale.bnd
bnd/derbyclient.bnd
bnd/derbynet.bnd
bnd/derbyoptionaltools.bnd
bnd/derbyshared.bnd
bnd/derbytools.bnd
bnd/locales.properties
{noformat}
Finally, I am getting an error with this patch when I try to build the jar
files. This happens regardless of whether I build production jars (set
"sane=true" in ~/ant.properties) or debug jars (set "sane=false" in
~/ant.properties).
Here's how I build the codeline:
{noformat}
# this runs cleanly
ant build
# this fails
ant buildjars
{noformat}
The error is:
{noformat}
meta-inf-common:
[copy] Copying 2 files to
/Users/rhillegas/derby/mainline/trunk/jars/insane/lists/META-INF
[exec] -----------------
[exec] Errors
[exec] 000: org.apache.derby.commons: Can not find JAR file
'derbyshared.jar'
[exec] -----------------
[exec] Warnings
[exec] 000: org.apache.derby.commons: Cannot find entry on -classpath:
../jars/sane/derbyshared.jar
[exec] 001: org.apache.derby.commons: Classpath is empty. Private-Package,
-privatepackage, and Export-Package can only expand from the classpath when
there is one
[exec] 002: org.apache.derby.commons: Unused Private-Package instructions,
no such package(s) on the class path: [*]
[exec] 003: org.apache.derby.commons: The JAR is empty: The instructions
for the JAR named org.apache.derby.commons did not cause any content to be
included, this is likely wrong
{noformat}
Any suggestions about how to remedy this? 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)
