Stefan Bodewig wrote:
On Wed, 09 Jun 2004, Peter Reilly <[EMAIL PROTECTED]> wrote:
In the 1.6 beta discussion, it was decided that the nested
elements of these tasks should also have the same xml ns as
the tasks themselves. The reason for this was consistency.
"consistency with the way XML namespaces are supposed to work" and
that's not been the only reason.
Granted.
wouldn't this here work?
<macrodef name="example">
<element name="files" implicit="yes"/>
<sequential>
<task xmlns="URI-for-prefix-x">
<files/>
<task>
<copy todir="z">
<files/>
</copy>
</sequential>
</macrodef>
no (in ant 1.6.1) see: http://marc.theaimsgroup.com/?l=ant-dev&m=107763945224538&w=2
I propose to allow nested elements discovered by reflection to
be in the tasks namespace and in the ant default namespace.
I think I know what you mean, let me try to clarify what I understand:
A nested element discovered by reflection is looked up in
(1) the task's namespace
(2) the namespace associated with Ant's core, no matter what the prefix of Ant's core may currently be and no matter what the default namespace currently is.
And (2) would only kick in if (1) fails.
I could support this proposal.
Excellent!
Peter
Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
