Dominique Devienne wrote:
From: Peter Reilly [mailto:[EMAIL PROTECTED]
wouldn't this here work?
no (in ant 1.6.1) see:
http://marc.theaimsgroup.com/?l=ant-dev&m=107763945224538&w=2
A nested element discovered by reflection is looked up in
> From: Peter Reilly [mailto:[EMAIL PROTECTED]
> >wouldn't this here work?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> no (in ant 1.6.1) see:
> http://marc.theaimsgroup.com/?l=ant-dev&m=107763945224538&w=2
>
> >A nested element discovered by
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
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 suppose
For antlib components the namespace of the tasks and
elements are decided by a xmlns:prefix="uri.." attribute.
This is quite nice and it is the proper way to have
different namespaces for different tasks with the same
localname. For example one could have a "deploy" task
in an antlib without worryi
