https://bz.apache.org/bugzilla/show_bug.cgi?id=66434
Bug ID: 66434
Summary: -Djava.security.manager=allow prevents correct %~dp0
expansion on Windows using <exec> when loaded from the
%PATH%
Product: Ant
Version: 1.10.13
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
Assignee: notifications@ant.apache.org
Reporter: robert.flahe...@oracle.com
Target Milestone: ---
Created attachment 38468
--> https://bz.apache.org/bugzilla/attachment.cgi?id=38468&action=edit
Test case: explode, change into root, run test.bat
I don't know if this is fixable or is just a known issue, but at least it can
help others trying to resolve similar issues.
When upgrading to 1.10.13 which has -Djava.security.manager=allow in ant.bat,
this caused failures in scripts that were run with <exec> and discovered along
the %PATH% and contained uses of %~dp0 (and I assume other expansions).
Instead of expanding to the drive/path of the executed script, it expanded to
the drive/path of the CWD.
It worked if:
1) I remove -Djava.security.manager=allow in ant.bat
2) I add vmlauncher="false" in the <exec>
--
You are receiving this mail because:
You are the assignee for the bug.
