ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conor MacNeill" <co...@cortexebusiness.com.au>
Subject RE: cvs commit: jakarta-ant WHATSNEW
Date Tue, 30 Apr 2002 00:45:54 GMT
> From: Alexey Solofnenko [mailto:alexeys@mdli.com]
>
> Hello,
>
>   the task <do> is what I need in my build files

Why? Could you explain how you would use it and why normal target dependency
and <antcall> operation cannot achieve what you want? I still am unclear
about the usecase.

> and it is not clear how
> <do> bypasses dependency checking more than <antcall>? They do
> not check for
> already executed dependencies at all.

<antcall> effectively runs a separate instance (context) of ant to process
the antcall request. Within this new context it performs dependency
checking. The fact that the same target can be run in both the main run and
the antcall run is entirely appropriate because they are being processed
within separate contexts. Cross-context dependency checking (which is what
<do> attempts to provide) is not something that should be done, IMHO.

Conor


--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message