Derby
  1. Derby
  2. DERBY-4500

CLASSPATH scripts should not exit on error

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.5.3.0
    • Fix Version/s: 10.5.3.2, 10.6.1.0
    • Component/s: Demos/Scripts
    • Labels:
      None
    • Environment:
      Unix platforms.
    • Urgency:
      Low
    • Issue & fix info:
      Known fix

      Description

      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.

      1. patch.diff
        1.0 kB
        Bryan Pendleton

        Issue Links

          Activity

            People

            • Assignee:
              Mike Matrigali
              Reporter:
              John Storta Jr.
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development