All releases of Ant prior to Ant 1.6 do not support XML namespaces. @@ -28,7 +28,7 @@ IIRC, and using any attribute starting with "xml" is actually strongly discouraged by the XML spec to reserve such names for future use.
-In build files using a lot of custom and third-party tasks, it is
easy to get into name conflicts. When individual types are defined, the
@@ -37,7 +37,7 @@
libraries of types using the <typedef> 'resource' attribute, the
build file writer has no chance to override or even prefix the names
supplied by the library.
Adding a 'prefix' attribute to <typedef> might have been enough,
@@ -76,7 +76,7 @@
Here, the namespace is set as the default namespace for the <task>
element and all its descendants.
The default namespace used by Ant is "antlib:org.apache.tools.ant".
@@ -89,7 +89,7 @@ -Almost always in Ant 1.6, elements nested inside a namespaced @@ -123,7 +123,7 @@ </my:task> -
Attributes are only used to configure the element they belong to if: @@ -162,7 +162,7 @@ XML-Schema (whether that's a good thing or not). The same is not true for elements from unknown namespaces, which result in a error.
-Now comes the difficult part: elements from different namespaces can be woven together under certain circumstances. This has a lot to do @@ -190,7 +190,7 @@ and elements like the builtin Ant conditions and selectors are not really types in 1.6. This is expected to change in Ant 1.7.
-The new AntLib