peter reilly wrote:
I would agree with most of what Nicola says. I think
that XML ns is a "heavy" solution for name clashing
of names defined in a antlib. Moreover I do not
think that the antlib needs to define a qualified name.
The "prefix" attribute idea of the <property/> task could
be used - even with the current <typedef/> command.
<typedef resource="net/sf/antcontrib/antcontrib.properties"
prefix="antcontrib"/>
Hm. How do you ensure that prefixes wont clash?
This also pretty much rules out validation or schema-directed
editing with a standard tool.
J.Pietschmann