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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] Target Milestone|--- |1.6 Version|1.1 |1.6Alpha (nightly) ------- Additional Comments From [EMAIL PROTECTED] 2003-09-02 15:47 ------- It hasn't popped up for two reasons: (1) <antcall> cannot live at the top level in any released version, so it hasn't been used that way by too many people yet. (2) it used to cause a build failure instead of an inifite loop for the first few months it was allowed there. The is code in Ant.java that tries to detect this, but since top-level tasks get executed at parser time now (they didn't in the initial version that allowed top-level tasks), the test kicks in too late. This is not a unique issue of having antcall at the top level, of course. <target name="foo"> <antcall target="bar"/> </target> <target name="bar" depends="foo"/> will have the same problem - and we've decided to not fix it as doing so would require too much logic that could be defeated by more complex builds anyway. We can and should test wether <ant> or <antcall> try to call the target they are defined in. And for tasks at the top level we must not allow calling the same build file at all. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
