Ian,
Let's first clear something up:
Perhaps I was making a wrong assumption : I assumed that these params would need to be defined at the top of the build file, and would be processed before any other global task or target. Am I wrong about this ?
Gert
----- Original Message ----- From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: "Nant-Developers (E-Mail)" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, August 22, 2004 5:07 AM
Subject: Re: [Nant-users] Params vs properties redux was: Nant .85 not working with Draco.Net
Gert Driesen wrote:
----- Original Message ----- From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Nant-Developers (E-Mail)" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, August 21, 2004 4:42 AM
Subject: [Nant-users] Params vs properties redux was: Nant .85 not working with Draco.Net
This seems to be causing a lot of grief. I'm really leaning towards having a list of <param> elements at the project level and allowing those and only those values to be passed on the commandline. I'm not sure how feasible that would be with the way we pass properties to nested builds but I think it would simplfy things a lot and add extra benefits. For example:
<project name="foo" >
<param name="param1" default="somevalue" description="my first commandline param" />
Ian, I like the idea in general, but I'm not sure if the default value for these properties is always known at design time, so users would have to resort to the overwrite attribute anyway ...
sorry - you've lost me. A default doesn't have to be specified - the default attribute wouldn't be required. Why would users have to resort to the overwrite attribute ?
In the future, I'm pretty sure we'll need to allow user input for specifying property values (like Ant) : when a certain property is not specified on the command line, the build author might want to have the user asked to input the value ...
so ? how is this an issue ?
Its great that we can use the description (and property name) in the project help, and we could even add a required attribute to specify whether a given property needs to be specified on the command line....
yep - that would be useful.
sorry - you've lost me again. I would see the <param> as inheriting from property and stored as a property - just readonly. the default just sets the value if one wasn't passed on the commandline - how is this too static ? Its no different from ueing <property> - its just more explicit -- ie its clear that params would be readonly whereas currently its not so clear that a property you specifiy in the buildfile 'becomes' readonly when you pass it via the commandline.
But as I said, I'm not sure the default attribute is all that useful, as its too "static" : when you need to execute other tasks/targets to determine the default value, the default attribute won't be of much use .... I understand the "problem" you're trying to tackle with this, but I'm not sure it will help users all that much ...
We would also need to think about how to deal with this for nested builds and included build files ...
sure. Ian
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
