I see your point and I agree. Bad idea. Hey Matt, put on the brakes! :) -----Original Message----- From: Dominique Devienne [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 3:00 PM To: Ant Users List Subject: RE: PropertySet use in macro
> From: Dick, Brian E. [mailto:[EMAIL PROTECTED] > > A target can do it. Why can't a macro? No, a target cannot do it. A target does nothing beside executing the tasks within. Passing properties to sub-processes as properties is natural and is an extensible way to pass in such properties, because it's open-ended. I prototyped that myself. What you propose is passing properties as XML attributes in essence, when these attributes are not open-ended. There is a fixed number of them for a given task, based on the task introspection rules. There is no reason you'd be able to inject in <macrodef> these properties as attributes, any more that you can do that with regular tasks. The fact that you can do something doesn't mean we should be doing it. Whatever you are trying to do you think needs such a hack, you'd better consider writing custom tasks for. --DD --------------------------------------------------------------------- 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]
