I would suggest one change to the script below.
# Minimal jar file to get JBoss started.
CLASSPATH=$JAR:$CLASSPATH
If CLASSPATH is empty or doesn't originally exists, then the below script causes
problems.
Brandon
>>> [EMAIL PROTECTED] 10/27/00 09:45AM >>>
Wait, my mistake. It's the CLASSPATH of $CLASSPATH:run.jar that
breaks, since if you run it from a different directory, there is no
"run.jar". So let me try a different fix:
JAR=run.jar
DIR=`echo $0 | sed -e "s/\(.*\)run\.sh/\1/"`
if [ ${DIR:-""} != "" ] ; then
JAR=$DIR$JAR
fi
# Minimal jar file to get JBoss started.
CLASSPATH=$CLASSPATH:$JAR
Aaron
On Fri, 27 Oct 2000, Rickard [iso-8859-1] +berg wrote:
> Hey
>
> Aaron Mulder wrote:
> > Yes - the Class-Path entries in run.jar.
>
> Are you sure? I think they are relative to run.jar and not from where
> one accessed run.jar...
>
> /Rickard
>
>
