Thanks to all who replied. That's the answer I needed. -- Charles Knell [EMAIL PROTECTED] - email
-----Original Message----- From: Grant Lewis <[EMAIL PROTECTED]> Sent: Fri, 12 May 2006 21:01:35 -0400 To: Ant Users List <user@ant.apache.org> Subject: Re: Iterate over "filelist" with java task? I generally define macrodef under project but it's also legal under target. Where you put the definition defines the scope of the macro. If you so choose, you can define macros in a project by themselves and use the import task to pull them into the current build file. Import and macros are a powerful combo when used together. Grant [EMAIL PROTECTED] wrote: > Thank you for your reply, but it answered a question I didn't ask. I want to > know what element can be the parent of a <macrodef>, not which elements a > <macrodef> can contain. Let me list some examples: > > Is a <macrodef> a child of <target>? > Is a <macrodef> a child of <project>? > Is a <macrodef> the child of some other element? --------------------------------------------------------------------- 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]
