[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038489#comment-17038489
]
Richard N. Hillegas commented on DERBY-7056:
--------------------------------------------
Thanks, Mark. I downloaded the bnd jar again and put it in tools/java. After
doing that, the buildjars target got a little further. Now "ant all buildjars"
errors out further on, as discussed above:
{noformat}
infowriter:
[propertyfile] Updating property file:
/Users/rhillegas/derby/mainline/trunk/classes/shared/org/apache/derby/info/shared/info.properties
meta-inf-common:
[copy] Copying 2 files to
/Users/rhillegas/derby/mainline/trunk/jars/sane/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
BUILD FAILED
{noformat}
The buildjars target raised this error even after I made the "all" target
depend on the "buildsource" target. This will need to be unravelled. I don't
think that I will have cycles for this until I have finished publishing the
10.15.2.0 release.
> 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, patch-20200209.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)
