Gert Driesen wrote:
....
I agree that it might indeed have been better, but these attributes are not
available for all elements (only for tasks, and some individual elements)
which would mean that you'd need a specific attributeconfigurator for this.
We could move the if/unless attributes (properties) from Task to Element,
but not all elements really need these attributes to be exposed.
Also, I'm not sure if it wouldn't break backward compatibility if we
suddenly stop initializing elements/tasks that should not be processed.
Right now, tasks can choose to ignore the if/unless attribute. I'm not
saying this is a good thing, ofcourse.
I discussed compatibility issues in my followup of 23 August, and
concluded there weren't any. I suppose a task implementation that
deliberately chose to ignore the if/unless attribute might be a
counterexample - if there are any (as opposed to those that ignore it
unintentionally) and if one could make a case for that particular task
needed it. Even so, that shouldn't be a serious problem for build files
- why would anyone put an if or unless attribute into a build file if
they expected it to be ignored?
I'm not proposing that the if/unless attributes be moved internally to
Element. I think there's a lot to be said for having a specific
mechanism for sharing some attributes among all tasks. The verbose
attribute and other logger/listener attributes come to mind as also
benefiting from being shared among all tasks (even though some of them
may apply to non-task elements).
Gary
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
