[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292607#comment-16292607
]
Bryan Pendleton commented on DERBY-6945:
----------------------------------------
It feels right, to me, to have sysinfo in derbytools. It's a tool.
Can't derbytools.jar reference derbyshared.jar in the MANIFEST? Does that
mechanism no longer work?
Speaking only for myself, I only use derbyrun.jar nowadays, so I always have
everything in my CLASSPATH. But, I realize I'm only using one of the many ways
to configure the derby classes into your classloader.
> 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)
