Gert Driesen wrote:
You mean an attribute that didn't exist ? Properties that don't exist cause
a build error already ...
Yep - that's what I was thinking.
But I agree that we should indeed have this mode (or just always run NAnt in
this mode, what do you propose) ...
In what cases should NAnt throw a build error :
- a system property that no longer exist
- an attribute/child element that is deprecated, and the IsError property of
the ObsoleteAttribute is set to true
- a task/type that is deprecated, and the IsError property of the
ObsoleteAttribute is set to true
- an attribute/child element that does not (or no longer) exist
+1 on all four. AFAIK, 2 and 3 are already done.
in what cases should NAnt output a warning (deprecated message) in the build
log :
- a system property that has been replaced/renamed (eg. replaced by a
function), but the original property still exists.
- an attribute/child element that is deprecated, and the IsError property of
the ObsoleteAttribute is set to false
- a task/type that is deprecated, and the IsError property of the
ObsoleteAttribute is set to false
+1 on all three here too.
Please correct me wherever necessary and add items to these lists
Looks good to me. The biggest issue I run into is renamed attributes.
Renamed sub-elements could also end up being a bit of a problem.
Should this be the default mode? I'm not sure about this one, but we
would need a way to run in less-strict mode.
Matt.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
