ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knuplesch, Juergen" <>
Subject AW: Setter in my own Anttask
Date Fri, 12 Feb 2010 14:59:52 GMT

Thanks for the link, but either I did not understand the docu correct or sth. wrong:

6.init() is called at run time. 
7.All child elements of the XML element corresponding to this task are created via this task's
createXXX() methods or instantiated and added to this task via its addXXX() methods, at run
8.All attributes of this task get set via their corresponding setXXX methods, at runtime.

Does this mean that the addConfigured methods should be called before the setters?

I experience that the setters are called before the add methods!!

So what is now the truth?

Greetings Juergen

J├╝rgen Knuplesch                    
-----Urspr├╝ngliche Nachricht-----
Von: Stefan Bodewig [] 
Gesendet: Freitag, 12. Februar 2010 15:43
Betreff: Re: Setter in my own Anttask

On 2010-02-12, Knuplesch, Juergen <> wrote:

> So I now start the application in every method that "runs" a nested 
> element. E.g. addConfigured... and some others.

> Is this a good way to do it?

Hard to tell.  Maybe it would be better to collect the nested elements and just do something
once execute has been called.

> Is it right that nested elements are added after the setters have been 
> executed?

It depends on whether you use createX(), addX() or addConfiguredX().
See "The Life-cycle of a Task" in


To unsubscribe, e-mail: For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message