[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048364#comment-17048364
]
Davide Grandi commented on DERBY-7056:
--------------------------------------
>one should "clone"
"one" was me : added *bnd.jar* download targets and updated build.xml until it
worked.
Not being an OSGI expert I made the minimal update that unlocked the build, so
maybe the results are OSGI-WRONG, but it's a common starting point for everyone.
I've attached a diff and a detailed operation log but, in short, the changes are
* downloading targets for bnd.jar - dumbly copied from those of junit.jar
* changed the references to bnd.jar from
<arg value="${bnd}"/>
to
<arg value="${javatools.dir}/bnd.jar" />
because bnd apparently never get defined and/or assigned.
MAYBE definition and/or assignment never got into to the patch : I've got some
problem while generating the new patch.
* commenting, in derbyshared.bnd the line
-includeresource: @derbyshared.jar!/META-INF/**,
@derbyshared.jar!/module-info.class
maybe because it seems to reference derbyshared.jar before it has been created.
In order to work in a repeatable fashion I suggest to :
- apply the patch in a clean checked out folder
- never "trust" 'ant clobber' but do a check with
svn status --no-ignore
and manually clean, from time to time, at least those files/folders
classes.pptesting
jars
classes
generated
javadoc
packageListLoc-j2ee-7
packageListLoc-se-9
release
changenumber.properties
before doing a full build
Cheers under an ongoing, but late, snowfall,
Davide
> 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, patch.20200229.1741.diff,
> patch.20200229.1741.diff, patch.20200229.1741.txt, patch.20200229.1741.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)
