[GERONIMO-6291] Cannot start server on windows caused by space chars in the related installation paths

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0, 3.0-beta-2
• Fix Version/s: 3.0-beta-2
• Component/s: startup/shutdown
• Security Level: public (Regular issues)
• Patch Info: Patch Available
• Assignee: Saphen Qiu
• Reporter: Ming Xia
• Created: 28/Feb/12 04:19
• Updated: 30/May/12 09:47
• Resolved: 27/Mar/12 15:08

Description

Having the latest Geronimo 3.0-beta-2 snapshot build, then doing these steps to reproduce the issue:
1. Install the jdk into a folder with space chars in the path
2. Install the geronimo server into a non-space path
3. set java_home=c:\path2jdkhome, not that no quotes there
4. run command: geronimo_home\bin\geronimo.bat run -l

You will see a failure something like this:
'""C:\Java\jdk1.6.0' is not recognized as an internal or external command,
operable program or batch file.

Basically, it is caused by the space characters in the windows file path. So to resolve the issues completely, we need to consider these scenarios:
1. JDK installation path includes spaces, and geronimo installation path does not
2. JDK installation path does not have, but geronimo has
3. Both JDK and Geronimo have space char in the path

Issue Links

• is duplicated by: GERONIMO-6358 Server can't be started if the build home contains space
• relates to: GERONIMO-6298 Geronimo won't start in command line