[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296884#comment-16296884
]
Bryan Pendleton commented on DERBY-6945:
----------------------------------------
No, I don't think you've misunderstood me. I just thought that the MANIFEST
mechanism caused those listed jars to be automatically included in the
CLASSPATH: https://docs.oracle.com/javase/tutorial/deployment/jar/downman.html
So I was hoping you wouldn't need to change
java/testing/org/apache/derbyTesting/functionTests/tests/tools/SysinfoLocaleTest.java
IOW, if derbytools.jar automatically pulls derbyshared.jar into the CLASSPATH,
and if SysinfoLocaleTest is specifying derbytools.jar on the CLASSPATH, then
why does it need to be changed to also specify derbyshared.jar?
> 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)
