Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
10.5.3.0
-
None
-
Unix platforms
-
Low
Description
On pages 13 and 14 of the 'Getting Started in Derby Guide', there are 3
scripts referenced that can be used to set the CLASSPATH environment
variable. setEmbeddedCP, setNetworkServerCP, & setNetworkClientCP. The
documentation indicates that the appropriate script should be run
depending on your needs.
Running the scripts like any other script does not work.
When a script is run, it launches a new shell for that script. The
CLASSPATH is set within that shell. Once the script is complete, that
shell exits and you are returned to your shell. The CLASSPATH is only
changed for the shell that the script was running in. The CLASSPATH in
your shell is unchanged.
$ ${DERBY_HOME}/bin/setNetworkClientCP
Will result in your CLASSPATH being unchanged.
In order for CLASSPATH in your shell to be updated, you have to run the
script from within your shell (not launch a new shell). This is done by
'sourcing' the script.
$ . ${DERBY_HOME}/bin/setNetworkClientCP
Will run the script within your shell resulting in your CLASSPATH being
updated.
The documentation is not clear on this.
Bug DERBY-4500 has been opened to address a related issue that will arise if/when the documentation is updated to reflect that the scripts should be sourced rather than run.