[
https://issues.apache.org/jira/browse/DERBY-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-3207.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
Issue & fix info: (was: [Patch Available])
Committed revision 924209.
> The bin scripts should be able to run when DERBY_HOME is not set
> ----------------------------------------------------------------
>
> Key: DERBY-3207
> URL: https://issues.apache.org/jira/browse/DERBY-3207
> Project: Derby
> Issue Type: Improvement
> Components: Demos/Scripts
> Affects Versions: 10.4.1.3
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.6.0.0
>
> Attachments: d3207.diff, d3207.stat
>
>
> The scripts under bin should be able to run without requiring the users to
> set DERBY_HOME explicitly. The script derby_common.sh, which is sourced by
> all the scripts under bin, contains code to detect DERBY_HOME based on the
> value of $0, but since the scripts need to know DERBY_HOME in order to source
> derby_common.sh, they still fail when DERBY_HOME is not set.
> When I removed this part of bin/ij
> -------
> 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
> fi
> . $DERBY_HOME/bin/derby_common.sh
> -------
> and in-lined the code in derby_common.sh in its place, I was able to run ij
> successfully by typing the command './bin/ij' without setting DERBY_HOME
> first.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
