Re: antcall with macrodef
Thanks, Fixed in cvs. Peter On Tuesday 14 October 2003 20:59, Shatzer, Larry wrote: > If your ant file contains antcall and you have macrodef's, and those > macrodefs have default attributes in the element, it throws off > this warning: > > Trying to override old definition of task > > See attached ant file as an example: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > run ant by itself, no errors or warnings, since antcall is never executed, > but if you run ant with antcall-test, you will see the warning. > > Of course, macrodef gets rid of the need for antcall is almost all cases, I > still however have a few antcalls I need to keep, until I figure a way to > convert them to using macrodef, and this warning has been bugging me that > there was something else deeply wrong with 1.6, but as you can see, the > execution happens as expected. > > -- Larry > > - > 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]
Re: antcall with macrodef
On Tue, 14 Oct 2003, Larry Shatzer <[EMAIL PROTECTED]> wrote: > If your ant file contains antcall and you have macrodef's, and those > macrodefs have default attributes in the element, it > throws off this warning: > > Trying to override old definition of task You'd see exactly the same if you used plain old at the top level, or maybe you would not as the code that generates the warning tries to see whether the old and new definitions use the same class and works differently. You could put your s into a target that your called target doesn't depend on. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
antcall with macrodef
If your ant file contains antcall and you have macrodef's, and those macrodefs have default attributes in the element, it throws off this warning: Trying to override old definition of task See attached ant file as an example: run ant by itself, no errors or warnings, since antcall is never executed, but if you run ant with antcall-test, you will see the warning. Of course, macrodef gets rid of the need for antcall is almost all cases, I still however have a few antcalls I need to keep, until I figure a way to convert them to using macrodef, and this warning has been bugging me that there was something else deeply wrong with 1.6, but as you can see, the execution happens as expected. -- Larry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
