Re: setenv.sh and CATALINA_BASE

2010-07-20 Thread Rainer Frey
On Thursday 15 July 2010 20:26:14 Christopher Schultz wrote: > Rainer, Hi, and sorry for the late reply. [I changed the order of some parts of your mail to reply > On 7/12/2010 9:14 AM, Rainer Frey wrote: > > I understand that, but would it be possible/good/not causing problems to > > change th

Re: setenv.sh and CATALINA_BASE

2010-07-15 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rainer, On 7/12/2010 9:14 AM, Rainer Frey wrote: > I understand that, but would it be possible/good/not causing problems to > change this to do CATALINA_BASE="$CATALINA_HOME first, so a setenv.sh can > rely > on CATALINA_BASE being set? I think I

Re: setenv.sh and CATALINA_BASE

2010-07-12 Thread Rainer Frey
On Monday 12 July 2010 14:44:19 Konstantin Kolinko wrote: > 2010/7/12 Rainer Frey : > > Hi, > > > > in the default case (just one instance, supplied start scripts), > > CATALINA_BASE is set to CATALINA_HOME. But this assignment, > > > > if [ -z "$CATALINA_BASE" ] ; then > > CATALINA_BASE="$CATAL

Re: setenv.sh and CATALINA_BASE

2010-07-12 Thread Konstantin Kolinko
2010/7/12 Rainer Frey : > Hi, > > in the default case (just one instance, supplied start scripts), CATALINA_BASE > is set to CATALINA_HOME. But this assignment, > > if [ -z "$CATALINA_BASE" ] ; then >  CATALINA_BASE="$CATALINA_HOME" > fi > > is done *after* reading setenv.sh. Is this for a specific

Re: setenv.sh and CATALINA_BASE

2010-07-12 Thread André Warnier
Rainer Frey wrote: On Monday 12 July 2010 12:17:40 André Warnier wrote: Rainer Frey wrote: On Monday 12 July 2010 10:56:19 André Warnier wrote: Rainer Frey wrote: Hi, in the default case (just one instance, supplied start scripts), CATALINA_BASE is set to CATALINA_HOME. But this assignment,

Re: setenv.sh and CATALINA_BASE

2010-07-12 Thread Rainer Frey
On Monday 12 July 2010 12:17:40 André Warnier wrote: > Rainer Frey wrote: > > On Monday 12 July 2010 10:56:19 André Warnier wrote: > >> Rainer Frey wrote: > >>> Hi, > >>> > >>> in the default case (just one instance, supplied start scripts), > >>> CATALINA_BASE is set to CATALINA_HOME. But this as

Re: setenv.sh and CATALINA_BASE

2010-07-12 Thread André Warnier
Rainer Frey wrote: On Monday 12 July 2010 10:56:19 André Warnier wrote: Rainer Frey wrote: Hi, in the default case (just one instance, supplied start scripts), CATALINA_BASE is set to CATALINA_HOME. But this assignment, in catalina.sh if [ -z "$CATALINA_BASE" ] ; then CATALINA_BASE="$C

Re: setenv.sh and CATALINA_BASE

2010-07-12 Thread Rainer Frey
On Monday 12 July 2010 10:56:19 André Warnier wrote: > Rainer Frey wrote: > > Hi, > > > > in the default case (just one instance, supplied start scripts), > > CATALINA_BASE is set to CATALINA_HOME. But this assignment, in catalina.sh > > if [ -z "$CATALINA_BASE" ] ; then > > > > CATALINA_BAS

Re: setenv.sh and CATALINA_BASE

2010-07-12 Thread André Warnier
Rainer Frey wrote: Hi, in the default case (just one instance, supplied start scripts), CATALINA_BASE is set to CATALINA_HOME. But this assignment, if [ -z "$CATALINA_BASE" ] ; then CATALINA_BASE="$CATALINA_HOME" fi is done *after* reading setenv.sh. Is this for a specific reason, or just

setenv.sh and CATALINA_BASE

2010-07-12 Thread Rainer Frey
Hi, in the default case (just one instance, supplied start scripts), CATALINA_BASE is set to CATALINA_HOME. But this assignment, if [ -z "$CATALINA_BASE" ] ; then CATALINA_BASE="$CATALINA_HOME" fi is done *after* reading setenv.sh. Is this for a specific reason, or just accidently? The reas