[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004536#comment-17004536
]
Richard N. Hillegas commented on DERBY-7056:
--------------------------------------------
I can only speculate about why buildjars does not depend on the buildsources
target.
The build instructions cited above will compile the product code but not the
testing classes. The "buildjars" target can be used to build jar files after
executing either the "buildsources" target or the "all" target. The "all"
target is more comprehensive. It also builds the regression tests and the demo
programs. When the "buildjars" target is run after only executing
"buildsources", it builds a vacuous derbyTesting.jar. Since "buildjars" can be
invoked after either of the compilation targets, it doesn't properly depend on
either of them.
They next question might be: why does Derby have 2 compilation targets? The
"buildsources" target lets you build the production jars from the Derby source
distribution. For licensing reasons, the junit jar file (needed for compiling
the tests) is not part of the Derby codeline. The user must download it
independently and accept the licensing terms. At one point, bundling Derby into
various Linux distros required us to provide a build scenario which let the
user build the production jars from the checked in source (what's in the source
distribution).
> 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)
