[jira] Updated: (DERBY-4501) CLASSPATH scripts do not work as defined in Getting Started in Derby Guide

["Bryan Pendleton (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Pendleton updated DERBY-4501:
-----------------------------------

    Attachment: docs.diff
                tgs26250.html

I agree that the different behavior of these scripts on Windows versus Unix/Linux
systems can be quite confusing. I tried to improve the documentation to
make this more clear.

Attached is a docs patch proposal ('docs.diff') and an HTML-formatted
version of the relevant page from the Getting Started guide.

I'm interested in whether people feel this makes the behavior more clear.


> 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, 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.