From: SourceForge.net <no...@so...> - 2004-01-05 19:34:46
|
Bugs item #871181, was opened at 2004-01-05 19:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871181&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Keenan Ross (keenanross) Assigned to: Nobody/Anonymous (nobody) Summary: Run.bat includes current directory in classpath Initial Comment: On MS Windows, if you have NOT set the JBOSS_CLASSPATH environment variable, and then execute the JBoss 3.2.2 run.bat from a DOS box, the server will echo: ======================================================================== . JBoss Bootstrap Environment . JBOSS_HOME: C:\jboss\jboss-3.2.2_jetty-4.2.11\bin\.. . JAVA: c:\j2sdk1.4.2_02\bin\java . JAVA_OPTS: -Dprogram.name=run.bat . CLASSPATH: ;c:\j2sdk1.4.2_02\lib\tools.jar;C:\jboss\jboss-3.2.2_jetty-4.2.11\bin\run.jar . ======================================================================== NOTE the leading semicolon in the value of the claspath, which the Java VM interprets as the current directory. If that directory contains extraneous .class or .property files, hard to track down problems can be introduced. The UNIX version of the start script, run.sh, does not suffer from this problem. Its logic, an explicit check for a non-existant JBOSS_CLASSPATH, could be used in run.bat to fix this bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871181&group_id=22866 |