Wouldn't something like make's ?= be useful here? The value is only assigned if it doesn't already have a value. That way you could tell by looking at the build file which variables were intended to be overriden on the command line. In nant's case, maybe an extra attribute on the property element could be used. Or maybe a different attribute name instead of "value", like "value-if-undefined".
-----Original Message----- From: Shaw, Gerry [mailto:grshaw@;ea.com] Sent: Saturday, October 19, 2002 2:04 PM To: Tomas Restrepo; Nant-Developers (E-mail) Subject: RE: [nant-dev] bug - Calling SysInfo Twice This behavior is for this situation: In your build file you define a property (ie, debug) to have a default value. <property name="debug" value="true"/> And you use that property in your build file. You then want to override that property on the command line so you use: nant -D:debug=false The nant console will add all properties on the command line as readonly. When the <property name="debug" value="true"/> task gets executed the property will not be set to true but keep the value specified on the command line. I believe this is a valid use case but I share your concerns about the subtle nature this might cause. I'm open to ideas to solve this. ------------------------------------------------------- This sf.net email is sponsored by: Access Your PC Securely with GoToMyPC. Try Free Now https://www.gotomypc.com/s/OSND/DD _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
