[
https://issues.apache.org/jira/browse/DERBY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805917#action_12805917
]
Dag H. Wanvik commented on DERBY-4501:
--------------------------------------
Actually, we don't provide a csh/tcsh sourcable setting script right now. We
may consider adding that, though.
As for your second attempt, I notice that the current UNIX shell script uses
the bash syntax for combined setting and exporting an environment variable, i.e.
export CLASSPATH= .....
In a classic Bourne shell, this is not allowed, one needs to write this in two
statements:
CLASSPATH=....
export CLASSPATH
which also works in bash, btw. So, for maximum usability I suggest we use the
latter form.
The scripts also contain a misleading "bang" header: "#!/bin/sh" indicating
Borne shell syntax,
when the syntax is reall bash. But the "bang" header should probably omitted
anyway, since the script is not meant for running but for sourcing?
Do the docs call for bash or just sh (Borne shell)?
> CLASSPATH scripts do not work as defined in Getting Started in Derby Guide
> --------------------------------------------------------------------------
>
> Key: DERBY-4501
> URL: https://issues.apache.org/jira/browse/DERBY-4501
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.5.3.0
> Environment: Unix platforms
> Reporter: John Storta Jr.
> Assignee: Bryan Pendleton
> Priority: Minor
> Attachments: docs.diff, docs.diff, tgs26250.html, tgs26250.html
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
