Gerry,
<<
I think the usage you want is somehting like:
nant -D:force=true build
This would need to set something (a property called nant.force?) that
tasks should look at? Ugg... I see you what you mean. It's getting a
bit ugly. Lets put that on the back burner until a good solution comes
along.
>>
This is a little different than other approaches we've had before, but
here's one approach I think could work: Don't make it an actual property!
Instead, make it an actual command line switch, like:
nant.Console.exe -force build
Then, have that set a real Property of the Project class with that value.
That way, tasks could just go ahead and use:
if ( Project.ForceBuild )
// do x
For all we care, this could be stored as an actual property in the project's
PropertyDictionary (say, nant.force as you suggest, or perhaps,
nant.project.force), so that it could be included in conditions in the
buildfile, but that would merely be an implementation detail as far as the
actual tasks is concerned.
How about that?
--
Tomas Restrepo
[EMAIL PROTECTED]
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
