Re: Quotations in a property get corrupted when passed as an arg

2005-04-13 Thread Mark Lundquist
On Apr 13, 2005, at 4:49 PM, Conor MacNeill wrote: Yes, easy in Unix. Can you do the same in Windows? You probably can, somehow. Well sure, of course. Um... a... :-) Touché! cheers, —ml— P.S.: Actually, we can do the same in Windows: http://cygwin.com Is that cheating? :-) :-)

Re: Quotations in a property get corrupted when passed as an arg

2005-04-13 Thread Conor MacNeill
Mark Lundquist wrote: On Apr 13, 2005, at 7:18 AM, Conor MacNeill wrote: There is not much Ant can do here - there is no real way for it to pass an argument that has quotes and spaces. How do you even do that yourself at the command line? Huh?! That's not even a problem... echo \"foo\"

Re: Quotations in a property get corrupted when passed as an arg

2005-04-13 Thread Mark Lundquist
On Apr 13, 2005, at 7:18 AM, Conor MacNeill wrote: There is not much Ant can do here - there is no real way for it to pass an argument that has quotes and spaces. How do you even do that yourself at the command line? Huh?! That's not even a problem... echo \"foo\" ls 'foo bar' — 

Re: Quotations in a property get corrupted when passed as an arg

2005-04-13 Thread Conor MacNeill
Oski Wee wrote: James Abley <[EMAIL PROTECTED]>wrote: James, thanks for your suggestion. I tried it, and it produces the same behavior as Namely, the actual argument Ant passes is "argument that has a literal " as part of its value", including the surround quotations. There is not much Ant

RE: Quotations in a property get corrupted when passed as an arg

2005-04-13 Thread Oski Wee
James Abley <[EMAIL PROTECTED]>wrote: James, thanks for your suggestion. I tried it, and it produces the same behavior as Namely, the actual argument Ant passes is "argument that has a literal " as part of its value", including the surround quotations. So, if I do an echo for each variable

RE: Quotations in a property get corrupted when passed as an arg

2005-04-13 Thread James Abley
On Tue, 2005-04-12 at 12:36, Oski Wee wrote: > >temp.cmd argument^ that^ has^ a^ literal^ ^"^ as^ part^ of^ its^ value > > > >The above is properly treated as 1 argument. > > Actually, turns out that the ^ does not even work from the command prompt. > > I guess I can try doing this: > temp.cmd "a

RE: Quotations in a property get corrupted when passed as an arg

2005-04-12 Thread Oski Wee
temp.cmd argument^ that^ has^ a^ literal^ ^"^ as^ part^ of^ its^ value The above is properly treated as 1 argument. Actually, turns out that the ^ does not even work from the command prompt. I guess I can try doing this: temp.cmd "argument that has a literal "" as part of its value" as a close appr

RE: Quotations in a property get corrupted when passed as an arg

2005-04-12 Thread Oski Wee
Thanks Bill for the suggestion. I tried it, but it did not work. Maybe I can give a better example that illustrates the problem. I want to pass my script an argument that has quotation marks and spaces inside it. Here is the contents of my script, temp.cmd: start "Arg1" cmd /K echo %1 start "

RE: Quotations in a property get corrupted when passed as an arg

2005-04-09 Thread Bill Rich
An Ant file is an XML file, therefore, you need to use the XML element for quote marks if you want the real quote mark to appear in the target. The XML element for quote mark is ". Carefully replace only those quote marks that need to be passed along with this element name and it should work. HTH