[JAMES-250] fail to start if installed under a "bin" directory

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 2.1.3, 3.0.0
• Fix Version/s: 2.3.0
• Component/s: James Core
• Environment: Windows 2000 Pro v5.00.2195; jdk 1.4.2_02-b03
• Assignee: Stefano Bagnara
• Reporter: Paul Gallagher
• Created: 09/Apr/04 02:09
• Updated: 21/Nov/07 08:31
• Resolved: 12/Aug/05 17:13

Description

if you install James under a "bin" directory, e.g. in C:\bin\james-2.1.3, the run.bat file fails to start because the trick with the ": operator" mis-calculates the PHOENIX_HOME.

This can be fixed by adding some crumbs to the env variable when figuring out PHOENIX_HOME. Example below is how I fixed it by adding the "*" crumb. Now I can run nicely under a "\bin" directory. A directory called "\bin*" is an impossibility, so it avoids this type of problem altogether.

{sorry, this diff is against a local copy I have, since I can't get my line terminators right working against the james cvs repo, but you should get the idea. Issue is still in the current HEAD}

— run.bat 2004/04/06 05:41:38 1.1
+++ run.bat 2004/04/06 05:45:36 1.2
@@ -39,10 +39,10 @@
if not "%OS%"=="Windows_NT" goto start

rem %~dp0 is name of current script under NT
-set PHOENIX_HOME=%~dp0
+set PHOENIX_HOME=%~dp0*

rem : operator works similar to make : operator
-set PHOENIX_HOME=%PHOENIX_HOME:\bin\=%
+set PHOENIX_HOME=%PHOENIX_HOME:\bin*=%

:start