Re: [NAnt-users] Command line properties - Can youexplainthismessage?

2008-03-03 Thread Brass Tilde
Ken Parrish <[EMAIL PROTECTED]> wrote: >> Eric, >> >> Good observation which I should have mentioned. The statement >> in my example is not really necessary--it just suppresses the error >> message generated by Nant. The code behaves correctly without the >> statement as was in my original exa

Re: [NAnt-users] Command line properties - Can you explainthismessage?

2008-03-03 Thread Ken Parrish
Eric, Good observation which I should have mentioned.  The statement in my example is not really necessary--it just suppresses the error message generated by Nant.  The code behaves correctly without the statement as was in my original example.  That is what was so confusing from the beginni

Re: [NAnt-users] Command line properties - Can you explainthismessage?

2008-03-03 Thread Eric Fetzer
That explains a lot. I always thought, "that message is lying" because, indeed, the property in the file DID get overwritten with my command line entry. Now that I realize the error is talking about the property statement in the file, I won't call NAnt a lier anymore. The only reason I put in

Re: [NAnt-users] Command line properties - Can you explainthismessage?

2008-03-03 Thread Ken Parrish
Alex, Yes, now I see what is going on.  Modified the script as follows to set a 'default' value in the event it is not specified on the command line as such:                                 This elicits the behavior that I want without the error message. Thanks, Ken Parrish

Re: [NAnt-users] Command line properties - Can you explainthismessage?

2008-03-03 Thread Roebuck, Alex
This also fooled me for a long time. The message saying "cannot overwrite read-only property" refers to the line in the NAnt build file trying to assign to a property that has been assigned on the command-line, not vice versa. From: [EMAIL PROTECTED] [m

Re: [NAnt-users] Command line properties - Can you explain thismessage?

2008-03-03 Thread Bob Archer
That won't work because a property set on the command line is read-only by design. (Overwrite by default is already set to true anyhow.) BOb From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Gainty Sent: Monday, March 03, 2008 11:

Re: [NAnt-users] Command line properties - Can you explain this message?

2008-03-03 Thread Martin Gainty
Hi Ken- 1) you'll need to set overwrite attribute to true e.g. 2)The user MUST HAVE write privileges to the folder in which he is writing so user fu can overwrite bar.txt chown fu bar.txt HTH Martin- - Original Message - From: Ken Parrish To: nant-users@lists.sourceforge.net

Re: [NAnt-users] Command line properties - Can you explain thismessage?

2008-03-03 Thread Bob Archer
After a bit of google, apparently yes, a property set on the command line is by default set to be a read-only property. (You learn something new every day eh?) BOb From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Archer Sent: Monday, Ma

Re: [NAnt-users] Command line properties - Can you explain this message?

2008-03-03 Thread Bob Archer
Interesting. I wonder if passing in a property value from the command line makes the property ready only. At least that is what appears to be happening. So, what do you want to happen here? If you want it to use the passed in value rather than the value in the script file? Use: ___

[NAnt-users] Command line properties - Can you explain this message ?

2008-03-03 Thread Ken Parrish
I am setting a property from the command line.  It seems to work, but I get a message indicating that I cannot overwrite the property, yet the property does in fact get set.  Can anyone help explain this? __ Nant Script:                     __ Command Line