Hi! I'm posting in ant-dev rather then ant-user
because I fear my question needs a deep
understanding of the ant implementation.
I made a class that can act both as a Task and a
passive ProjectComponent. That is, if defined in
a target or as a direct child of <project> it's execute()
method is called, if defined as a nested element not.
The problem is that when acting as a task the attributes
are evaluated if they contain property references (${x}),
when acting as a passive element not (you'd have to do
it explicitely by calling replaceProperties()).
Is it possible to avoid property replacement in the task
attributes in a clean and safe way?
I wanted to try to override Task.maybeConfigure() but
there are the RuntimeConfigurable and UnknownElement
I'm not familiar with.
Sorry if it's a stupid question or I oversaw something evident.
Thanks,
Stefano Marsili
---------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+
countries) for 2ยข/min or less.
