You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by bu...@apache.org on 2001/10/13 16:35:48 UTC
DO NOT REPLY [Bug 4151] New: -
Phoenix run.bat problem on Win2K Pro (w/ delayed environment var expansion)
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=4151>.
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=4151
Phoenix run.bat problem on Win2K Pro (w/ delayed environment var expansion)
Summary: Phoenix run.bat problem on Win2K Pro (w/ delayed
environment var expansion)
Product: Avalon
Version: unspecified
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Minor
Priority: Other
Component: Phoenix
AssignedTo: avalon-dev@jakarta.apache.org
ReportedBy: coopman@jumpstart-tech.com
Phoenix 4.01a
Windows 2000 Pro
If you try to run the bin\run.bat script from a command shell which has ENABLED
delayed environment variable expansion (e.g. C:> cmd /V:ON), the java command
invoking Phoenix will fail with a usage message.
This is due, I think, to the presence of a '!' in the java.policy path declared
for a policy file inside a Jar file.
The workaround is to make sure you use a shell with this feature disabled (this
is by default, or explicitly as C:> cmd /V:OFF)
It is a useful feature for shell scripting, but I can't determine if there is
an alternate way to specify the policy path, or whether there is a way to
escape the windows shell interpretation of the '!' in terms of delayed
expansion.
Thought you should know about this.
Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org