[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296067#comment-16296067
]
Bryan Pendleton commented on DERBY-6945:
----------------------------------------
Hi Rick, thanks for the thorough explication of the testing changes you made.
I am still puzzled as to why it isn't sufficient to have derbyshared.jar listed
in the MANIFEST
of derbytools.jar. It seems like derbyshared.jar should be in the MANIFEST of
all the other
jar files, and then we should be all set.
But I am fine with the testing changes that you propose.
Thanks for working on this complex and thorny problem. I'm following along with
the
discussions, but don't have any additional suggestions to make.
> 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,
> derby-6945-02-ab-newDerbySharedJar.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)
