Summary: | Running Ant from command line fails if property contains a comma | ||
---|---|---|---|
Product: | Ant | Reporter: | Mark Melvin <mark.melvin> |
Component: | Core | Assignee: | Ant Notifications List <notifications> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 1.7.0 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP |
Description
Mark Melvin
2009-01-19 08:10:54 UTC
Sorry, but this is not a bug. The command shell (DOS) in this case is the one interpreting the command line before Ant sees it, and the quoting to be done is Shell dependent. We can't do anything about this. --DD Well, I think things could be worked around in Ant.bat as you are exposing the shell's argument weaknesses by rebuilding all the args using SHIFT. This forces you to accept the result - which is that the DOS prompt splits arguments on all delimiters. If you didn't use SHIFT you would not have the problem. If you can provide a functionally equivalent ant.bat which does not exhibit the issue you reported regarding comma handling, we'd gladly take it, although the Ant team is quite reticent to ant.bat changes in general since they tend to be so brittle, as you probably well know since you mention DOS' weakness in the domain. Maybe you can substitute ant.bat for a .bat of your own doing? |