Still the overall problem I have with customizing Ant is the over-usage of "private". It also bites at other places, ComponentHelper is just an example.
On the contrary, it's a Good Thing (TM) Ant's purpose is as a build tools, not a Java library. Keeping its internals private allows future refactoring which do not break BC, or minimize BC issues. It's a lot easier to open up an API here and there, when there's a good case for it, rather than leaving everything "protected" or public. <presetdef> is just syntactic sugar, and is better not used IMHO. But if you persist on wanting to overuse it, concentrate your energy on simply adding an attribute to presetdef to ignore overrides (with all that entails), and provide a patch. Or better yet, use a my- prefix for your presets, so as not to confuse people with tasks that look like plain Ant tasks, but don't behave the same because their defaults have been changed. This is most likely a maintenance issue, and a violation of the "principle of least surprise". Good luck. I'll get down from my soap box now ;-) --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
