[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6945:
---------------------------------
Attachment: derby-6945-01-aa-remove_derbyPreBuild_dep.diff
Attaching derby-6945-01-aa-remove_derbyPreBuild_dep.diff. This patch moves the
declaration of a constant out the derbyPreBuild package and into one of the
services packages. This causes compiled product files to no longer reference
the derbyPreBuild package. That, in turn, removes derbyPreBuild from the jdeps
graph of module dependencies. I will run tests.
Touches the following files:
----------------------------
M
java/engine/org/apache/derby/iapi/services/info/ProductVersionHolder.java
M java/engine/org/apache/derby/iapi/services/info/PropertyNames.java
Move the constant into PropertyNames.
----------------------------
M java/build/org/apache/derbyPreBuild/ReleaseProperties.java
M java/build/org/apache/derbyPreBuild/build.xml
Move the constant out of ReleaseProperties and adjust the pre-build so that the
PropertyNames are comiled along with the derbyPreBuild package.
> Re-package Derby as a collection of jigsaw modules
> --------------------------------------------------
>
> Key: DERBY-6945
> URL: https://issues.apache.org/jira/browse/DERBY-6945
> Project: Derby
> Issue Type: Improvement
> Affects Versions: 10.13.1.2
> Reporter: Rick Hillegas
> Attachments: derby-6945-01-aa-remove_derbyPreBuild_dep.diff,
> jdeps.out.tar
>
>
> Once we commit to building with Java 9 (see DERBY-6856), we should consider
> re-packaging Derby as a set of jigsaw modules. This would result in a
> different set of release artifacts. This might be a good opportunity to
> address the Tomcat artifactory issues raised by issue DERBY-6944.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
