See comment below.
From: "Gert Driesen" <[EMAIL PROTECTED]>
> > From: "Clayton Harbour" <[EMAIL PROTECTED]>
[snip]
> [TaskName("cvscheckout")]
> [TaskName("cvs-checkout", Obsolete=true, ObsoleteMessage="Use
<cvscheckout>
> instead.")]
> public class CheckoutTask : AbstractCvsTask {
>
> What do you think ? Got any other (and better) proposals ?
That is an option but I like the idea of allowing only a single [TaskName]
attributes on a class. I don't think we allow (or should) a class to
implement more than one task (name).
>
> This might appear simple, but it has quite some impact on our
> attribute-based initialization code and our documentation generation
process
We could go the route of using a new attribute to mark obsolete tasks. It
would work something like this:
[TaskName("cvscheckout")]
[ObsoleteTask("Use <cvscheckout> instead.")]
public class CheckoutTask : AbstractCvsTask {
....
}
We will probably also want to create corresponding [ObsoleteTaskAttribute]
and [ObsoleteTaskElement] attributes if we go with this method.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
