ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeffrey E Care <>
Subject Re: Guidelines for executing delegate tasks?
Date Thu, 03 Nov 2005 03:47:13 GMT
The more I think about it the more I'm convinced that the best way to 
address this problem is to change the thread/task registration to be a 
stack rather than the current single value implementation. This would 
safely handle any rogue usage of "perform" where "execute" would be 
preferred, while maintaining the current behavior.

Any thoughts?
Jeffrey E. Care (
WebSphere v7 Release Engineer
WebSphere Build Tooling Lead (Project Mantis)

Stefan Bodewig <> wrote on 11/02/2005 03:38:53 PM:

> First of all, what you describe is what I've mentioned in
> <> and
> yes, using perform looks like the problem here.
> I'd be +1 to switching to execute in this case.
> On Tue, 1 Nov 2005, Jeffrey E. Care <> wrote:
> > So, getting to the point, is there a general policy regarding
> > "execute"/"perform" for delegate task instances?
> I don't think there is.  We've mentioned the difference between
> perform an execute in context with TaskContainers.  "If you want build
> events from the "delegate" tasks, use perform, otherwise use execute",
> would be my advice, but I may be overlooking something.
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message