DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22759>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22759 antcall at top level causes infinite loop ------- Additional Comments From [EMAIL PROTECTED] 2003-09-02 17:31 ------- That makes sense. However antcall needs to call the same file in all cases so it sounds like you are banning antcall from the top level? Perhaps there is a way to scan ahead for the target and grab it? A quick pass over the top level of the build file to collect the targets first would give us a list of targets to invoke rather than calling the whole file over (if it is not already done that way). It should not be too supprising to the user if top level properties defined after the antcall are not expanded when the target is invoked. (and similar issues with other things that happen at the top level after the antcall). What I can't seem to figure out myself is would such a strategy force us to change the behavior of antcall in a non-backwards compatable manner. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
