ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From peter reilly <>
Subject Re: [Patch] namespace and antlib
Date Fri, 15 Aug 2003 14:08:02 GMT
On Friday 15 August 2003 12:06, Stefan Bodewig wrote:
> On Fri, 15 Aug 2003, peter reilly <> wrote:
> > This does not work for the new types of definitions (macrodef,
> > presetdef, and scriptdef), so I am thinking of changing this to
> > always do the warning (unless they are the same definition as
> > reported by the AntTypeDefinition).
> A simple test of whether this is a good idea is a build file with a
> <taskdef> at the top-level and a target that contains <antcall>.  You
> are not supposed to get a warning when running the antcall.

Ah! Thanks,
I will try that.

In any case I have had another look at the original code, and
understand it a little better.

I am able to suppress the warning for <taskdef/> and <typedef/>
by using the original logic. But have ran into issues
with the other definitions (i.e. are all the unknown elements
the same?, is the script the same etc..)


> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message