--- Dominique Devienne <[EMAIL PROTECTED]> wrote:
> 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.
That's awfully hardline. :) One thing that did occur
to me that is kind of a negative is that the
<propertyset> is not a child of <macrodef>, but a
child of the MacroInstance.
This brings me back to local properties. So when (!)
the <local> patch goes in, an optional usage could be
to omit the name and value attributes, instead
specifying a <propertyset>. This would only make
sense with a <mapper>, but wouldn't hurt anything
without.
Now, then...
-Matt
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
