db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (DERBY-4500) CLASSPATH scripts should not exit on error
Date Wed, 02 Feb 2011 23:38:29 GMT

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

Kathey Marsden reopened DERBY-4500:

Reopen for backport

> CLASSPATH scripts should not exit on error
> ------------------------------------------
>                 Key: DERBY-4500
>                 URL: https://issues.apache.org/jira/browse/DERBY-4500
>             Project: Derby
>          Issue Type: Bug
>          Components: Demos/Scripts
>    Affects Versions:
>         Environment: Unix platforms.
>            Reporter: John Storta Jr.
>            Assignee: Bryan Pendleton
>            Priority: Minor
>             Fix For:
>         Attachments: patch.diff
> This applies to the following
> setEmbeddedCP
> setNetworkServerCP
> setNetworkClientCP
> Bug DERBY-4283 references this issue, but only with regard to the setEmbeddedCP script.
 That bug also indicates the issue was resolved in 10.5.2, but I am looking at 10.5.3 and
I still see the exit command in the script.
> The proper way to use these CLASSPATH scripts is to source them rather than run them.
> . $DERBY_HOME/bin/setNetworkServerCP
> Doing so will run the script in the current shell.  If the scripts issue an exit upon
encountering an error, then the users shell will exit as well.
> This is the relevant section of the scripts
> if [ -z "$DERBY_HOME" ] ; then
>   echo "Error: DERBY_HOME is not set. Please set the DERBY_HOME environment variable"
>   echo "to the location of your Derby installation."
>   exit 1   #<<<<This will exit the users shell if the script is sourced
> fi
> The scripts should generate a message if DERBY_HOME is not set, but should not issue
an exit command.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message