One can use the "configured" form of the add method.
public void addConfiguredCommandline(Commandline c) {
}
Ant will set the attributes / elements on Commandline c before
calling addConfiguredCommandline(Commandline c)
Peter
On 3/23/06, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
>
> On Tue, 14 Mar 2006, Daniel Kasmeroglu
> <[EMAIL PROTECTED]> wrote:
>
> > Generally this is okay for ANT because it seems that ANT creates the
> > child-elements before setting the attributes, so this won't produce
> > an error (correct me if I'm wrong). But I would like to know if
> > this is part of ANT's design so a developer must take this into
> > account when the API is used directly or is it just an unproper way
> > of implementation within the JUnitTask ?
>
> See the "Developing with Ant" -> "Writing Your Own Task" -> "Lifecycle
> of a Task" section in the Ant manual. child elements are handled in
> step 6, attributes in step 7. So yes, this is part of Ant's contract
> with tasks.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
