Nicola Ken Barozzi wrote:
[returned from holiday, happy to read the list again :-) ]
Jose Alberto Fernandez wrote, On 22/08/2003 14.58:
From: Gus Heck [mailto:[EMAIL PROTECTED]
...
If macro definitions are available to sub builds, then your 3rd case might occur, but I don't think it would be good to allow macros to be called across build file boundaries. builds would be almost unintelligible without tracking down the macros from other files.
This is all regular kosher ANT stuff, up to this day, <taskdef/>s get
inherited, they do not need to be redeclared for the task to be
available during the <antcall/>.
...
We already have a solution for the case of <taskdef> I would just like the behavior on both cases to be the same, so to reduce the leaarning curve.
What about making them part of antlibs too?
How does a macro defined in the build become an antlib?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
