DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27310>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27310 CLASSPATH reset in intialization script [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2004-02-28 20:39 ------- Providing the user/administrator a way to specify envirnoment variables is a feature, erasing them afterwards is an engineering fault. If it IS a feature, it is woefully underengineered. The reinitialization of the CLASSPATH happens very late in the startup process, after the CLASSPATH has been amended by other scripts that are run earlier in the startup sequence. Namely, it will rewrite the CLASSPATH after the setenv.bat file (if you specify one) has been run. This means that if you change the CLASSPATH, an environment variable, in the setenv.bat script, then your changes will be lost. It is quite clear then that this can not be the desired function, namely; creating a special hook in the startup sequence to allow you to change environment variables, and then afterwards overwriting changes that were made. Obviously either the line in setclasspath.bat needs to be altered as suggested, or the call to setenv.bat moved farther along in the startup sequence after the offending line of code, or the call to setenv.bat removed entirely. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
