Re: cvs commit: jakarta-tomcat-4.0/catalina/src/binsetenv.shcatalina.sh tool-wrapper.sh

2001-11-27 Thread Jon Stevens
on 11/27/01 3:09 PM, Patrick Luby [EMAIL PROTECTED] wrote: Jon, What I could do is not distribute the setenv.sh file and, instead, check for the existence of this file. If it exists (which would only occur if the user has created the file), then catalina.sh and tools-wrapper.sh would

Re: cvs commit: jakarta-tomcat-4.0/catalina/src/binsetenv.shcatalina.sh tool-wrapper.sh

2001-11-27 Thread Patrick Luby
Jon, Jon Stevens wrote: [snip] Just as a side note, we need to be more cautious about upgrades and how users perform them. The server.xml is a big sore spot as well because that is another file that needs to be changed by the users. Thanks for catching this in my initial commit. I have

Re: cvs commit: jakarta-tomcat-4.0/catalina/src/binsetenv.shcatalina.sh tool-wrapper.sh

2001-11-27 Thread Remy Maucherat
on 11/27/01 3:09 PM, Patrick Luby [EMAIL PROTECTED] wrote: Jon, What I could do is not distribute the setenv.sh file and, instead, check for the existence of this file. If it exists (which would only occur if the user has created the file), then catalina.sh and tools-wrapper.sh would

RE: cvs commit: jakarta-tomcat-4.0/catalina/src/binsetenv.shcatalina.sh tool-wrapper.sh

2001-11-27 Thread Bernard D'Have
: jakarta-tomcat-4.0/catalina/src/binsetenv.shcatalina.sh tool-wrapper.sh on 11/27/01 3:09 PM, Patrick Luby [EMAIL PROTECTED] wrote: Jon, What I could do is not distribute the setenv.sh file and, instead, check for the existence of this file. If it exists (which would only occur