[
https://issues.apache.org/jira/browse/DERBY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805545#action_12805545
]
Kim Haase commented on DERBY-4501:
----------------------------------
This is very useful info to have -- thanks, Bryan.
I have a couple of language suggestions --
Being kind of a stickler about "differently than" I would suggest changing the
sentence to either
"Note that these scripts behave slightly differently on UNIX systems and on
Windows systems."
or
"Note that these scripts behave slightly differently on UNIX systems from the
way they behave on Windows systems."
Also, the long sentence starting with "Otherwise" might better be broken into
separate sentences -- perhaps the UNIX and Windows info can be in separate
paragraphs.
"On UNIX systems, you need to use the "dot" or "source" command to ensure that
the script is run in the calling shell's environment. Otherwise, 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 changed only for the shell that the script was
running in. The CLASSPATH in your shell is unchanged."
That said, I happen to be running in a C shell on Solaris, and I can't make the
scripts work at all, even if I switch to a Bourne shell. Neither source nor dot
seems to work. This may be of no concern to anybody, things being how they are
...
I already have the classpath set, so that I can build the Derby docs -- you
probably do too.
jdench 49 =>setenv DERBY_HOME /home/chaase/db-derby-10.5.3.0-bin
jdench 50 =>echo $CLASSPATH
.:./lib/fop.jar:./lib/avalon-framework-cvs-20020806.jar:./lib/batik.jar
jdench 51 =>echo $DERBY_HOME
/home/chaase/db-derby-10.5.3.0-bin
jdench 52 =>source $DERBY_HOME/bin/setEmbeddedCP
Missing ]
jdench 53 =>. $DERBY_HOME/bin/setEmbeddedCP
/home/chaase/javaee6-sdk/glassfish/bin/.: Permission denied
jdench 54 =>echo $CLASSPATH
.:./lib/fop.jar:./lib/avalon-framework-cvs-20020806.jar:./lib/batik.jar
jdench 56 =>/bin/sh
$ echo $CLASSPATH
.:./lib/fop.jar:./lib/avalon-framework-cvs-20020806.jar:./lib/batik.jar
$ echo $DERBY_HOME
/home/chaase/db-derby-10.5.3.0-bin
$ . $DERBY_HOME/bin/setEmbeddedCP
CLASSPATH=/home/chaase/db-derby-10.5.3.0-bin/lib/derby.jar:/home/chaase/db-derby-10.5.3.0-bin/lib/derbytools.jar:.:./lib/fop.jar:./lib/avalon-framework-cvs-20020806.jar:./lib/batik.jar:
is not an identifier
$ echo $CLASSPATH
.:./lib/fop.jar:./lib/avalon-framework-cvs-20020806.jar:./lib/batik.jar
> 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.
