Sounds good to me. Then I can get rid of the extra code in the macro that removes the warning.
-David -----Original Message----- From: Peter Reilly [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 16:11 To: Ant Users List Subject: Re: Why "Trying to override old definition of task xxx" message? I have implemented a test for this in ant cvs. So ant 1.6.3 should not show the "task override" warning for this situation. Peter Peter Reilly wrote: > The problem is most likely the default value for the "dest" attribute > if you are using <ant>, <antcall> or <subant> > > For example: > <project default="caller"> > <macrodef name="copy.compile.post"> > <attribute name="dest" > default="${dir.bin.work}"/> > <sequential> > </sequential> > </macrodef> > <target name="called"> > </target> > <target name="caller"> > <property name="dir.bin.work" value="."/> > <antcall target="called"/> > </target> > </project> > > this issue was reported as bug 31215. > http://issues.apache.org/bugzilla/show_bug.cgi?id=31215 > > This issue are happened a number of times, so I think > that the ant code could be modified to allow macrodefs that are > different in > contents (due to property values changing) but otherwise the same to > be treated as "similar" - resulting in a log message at verbose level > and > not at warning level. > > Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
