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?
:-) :-)
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\"
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'
—
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
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
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
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
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 "
EMAIL PROTECTED]
Sent: Saturday, April 09, 2005 6:21 AM
To: user@ant.apache.org
Subject: Quotations in a property get corrupted when passed as an arg
I am trying to read a property from my build.properties file and pass it as
an to a script that I . The problem is that the property value
contains li
I am trying to read a property from my build.properties file and pass it as
an to a script that I . The problem is that the property value
contains literal quotation marks inside, and they get corrupted during the
process.
This is the property in build.properties:
jade.arg=AgentName:com.packa
10 matches
Mail list logo
