[
https://issues.apache.org/jira/browse/DERBY-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682861#comment-16682861
]
Rick Hillegas commented on DERBY-7016:
--------------------------------------
Attaching derby-7016-01-aa-addSharedModule-setModulepath. This patch adds the
shared module to the classpaths built by the classpath-building scripts and
makes the scripts set a MODULEPATH variable also.
Running with these scripts flushed out a problem with the tool module: its
dependencies on the engine and client modules needed to be optional, as
indicated by the new Derby module diagrams.
I hand-tested the unix scripts with a simple heartbeat program. I tested an
embedded connection to a Derby database and a remote client connection. I will
run full tests.
I will look for a machine on which to test the Windows scripts.
{noformat}
--------------------------
M bin/setEmbeddedCP
M bin/setEmbeddedCP.bat
M bin/setNetworkClientCP
M bin/setNetworkClientCP.bat
M bin/setNetworkServerCP
M bin/setNetworkServerCP.bat
Add derbyshared.jar to the CLASSPATH variable set by these scripts.
--------------------------
M java/org.apache.derby.tools/module-info.java
Relax the tool module's dependencies on the engine
and client modules so that they are optional.
{noformat}
> Adjust the set*CP scripts to include derbyshared.jar and to set a MODULEPATH
> variable as well
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-7016
> URL: https://issues.apache.org/jira/browse/DERBY-7016
> Project: Derby
> Issue Type: Bug
> Components: Demos/Scripts
> Affects Versions: 10.15.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Priority: Major
> Fix For: 10.15.0.0
>
> Attachments: derby-7016-01-aa-addSharedModule-setModulepath.diff
>
>
> The classpath-setting scripts need to include derbyshared.jar in the
> classpath and set MODULEPATH as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
