> 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 >
That's pretty much what I was thinking, too. I think it's not a task attribute at all, but rather an attribute of the current instantiation of NAnt. > 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? I think making it a property that can be included in other conditions is a great idea. Eric. ------------------------------------------------------- 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
