This is a good point and idea. It seems like a valid feature.
I don't think that we need to change the structure of the core all that
much. I've written a copy constructor for Target that resets the
_hasExecuted bit so each copy can be executed again.
//Copy ctor
public Target(Target t) {
this._name = t._name;
this._desc = t._desc;
this._dependencies = t._dependencies;
this._ifDefined = t._ifDefined;
this._unlessDefined = t._unlessDefined;
this._targetNode = t._targetNode;
this._hasExecuted = false;
}
With this in hand, a specific Task should be easy to write. This change
is pretty small and should make it easy for people to extend, or execute
arbitrary targets at will.
Sound good to all? (Unless I hear otherwise, I'll commit later today. :)
> -----Original Message-----
> From: [EMAIL PROTECTED]
[mailto:nant-developers-
> [EMAIL PROTECTED]] On Behalf Of Brad Wilson
> Sent: Friday, May 17, 2002 9:43 AM
> To: NAnt Developers
> Subject: Re: [nant-dev] Possible bug calling the same target more than
onc
> e
>
> Browning, Don wrote:
>
> > Does Ant have anything like a subroutine task?
>
> Not that I'm aware of. And you couldn't do it at the task level,
anyway.
> That's too late. It would have to be something added to the core of
NAnt
> as
> a parallel (but separate) thing like "target".
>
> Could it be done? Yes. Should it? I think so. What do others think?
>
> Brad
_______________________________________________________________
Hundreds of nodes, one monster rendering program.
Now that�s a super model! Visit http://clustering.foundries.sf.net/
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
