https://bz.apache.org/bugzilla/show_bug.cgi?id=61649
--- Comment #20 from Stefan Bodewig <[email protected]> --- Yes, it does. It really is your "build.sh" script that breaks the arguments. Here is an example $ cat > /tmp/test.xml <project> <echo>$${foo}'s value is "${foo}"</echo> </project> ^D $ ant -f /tmp/test.xml Buildfile: /tmp/test.xml [echo] ${foo}'s value is "${foo}" BUILD SUCCESSFUL Total time: 0 seconds $ ant -f /tmp/test.xml -Dfoo=bar Buildfile: /tmp/test.xml [echo] ${foo}'s value is "bar" BUILD SUCCESSFUL Total time: 0 seconds $ ant -f /tmp/test.xml -Dfoo="bar baz" Buildfile: /tmp/test.xml [echo] ${foo}'s value is "bar baz" BUILD SUCCESSFUL Total time: 0 seconds Even $ ant -f /tmp/test.xml -Dfoo="bar -Xmx1024m baz 'and something \"strangely\" quoted'" Buildfile: /tmp/test.xml [echo] ${foo}'s value is "bar -Xmx1024m baz 'and something "strangely" quoted'" BUILD SUCCESSFUL Total time: 0 seconds It is build.sh that turns the single property into three separate command line args. The old script seems to have combined them correctly back into a single argument by accident. Now that we've fixed the ant wrapper script you must ensure build.sh works correctly for your quited arguments as well. -- You are receiving this mail because: You are the assignee for the bug.
