On Thursday 06 November 2003 11:54, peter reilly wrote:
>
> However, I understand the problem of writing schemas, using xml editors and
> also the fact that it is a little strange ...
>
> So now I think that the nested elements should have the
> namespace of the enclosing element (except for typedef'ed elements)
>
> I have a patch ready to do this (enclosed) (without unit tests)
> and am ready to commit.
>
One oddity is that the implementation of elements is now
exposed.
For example the <for> task from ant-contrib has a <sequential>
nested element, <outofdate> also has a <sequential>. The first
is implemented by addTask(Task) and the second is implemented
by addSequential(Sequential), this means that with the new
ns rules one needs to do:
<ac:for param="file">
<ac:path>
<ac:fileset dir="${test.dir}/mains" includes="*.cpp"/>
</ac:path>
<sequential>
<ac:outofdate>
<ac:sourcefiles path="${file}"/>
<ac:targetfiles path="${file}.txt"/>
<ac:sequential>
<echo>the ${file} was outofdate</echo>
</ac:sequential>
</ac:outofdate>
</sequential>
</ac:for>
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
