Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 4.3.1
-
Fix Version/s: None
-
Component/s: Installer
-
Labels:None
-
Environment:WXP SP2, Java 1.5
-
Number of attachments :
Description
Hi
I have a parsable file that contains a JVM property expressed as:
<config location="-Dlog4j.properties=file:///$INSTALL_PATH/cfg/log4j.xml">
When installing the product into C:\Program Files, the substittued value is
<config location="-Dlog4j.properties=file:///C:\Program Files/cfg/log4j.xml">
which leads to an exception or a misuse of the configuration file.
Thus, IsPack on WXP, should use the short standard 8.3 name instead of the full path name to avoid this blank-in-path problem.
I understand the problem, but I'm not sure about the solution you suggested.
The right solution here would be to make whitespaces simply work (with a fix or workaround), but not to fall back using 8.3 names, in case the operating system and Java normally fully supports whitespaces in file names.