ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hal Hildebrand \(web\)" <>
Subject Re: Ant 1.5Beta3 Released
Date Tue, 25 Jun 2002 15:17:24 GMT
The issue is that I have build files that are designed to be called
independently of one another, but also designed to be nested.  That's
why each build file defines the same tasks.  I'm not sure how one could
achieve this result - which I think is a good pattern - without running
into this problem, short of putting all the task jars in ant/lib before
they are invoked.  Something that is tricky to do at best, and certainly
can get ugly and mess up the logs if exec is involved.

Perhaps all that is needed is to add an optional attribute to the
taskdef - say "ignoreOverride" - that if true will make the messages
verbose instead of warn?

In any event, since I seem to be the only one with the problem, I'll
stop my whining...  :)

Thanks for looking at this.


----- Original Message -----
From: "Diane Holt" <>

> --- "Hal Hildebrand (web)" <> wrote:
> > Why can't it just be MSG_VERBOSE instead of MSG_WARN?  Seems more
> > reasonable to me....  <g>
> Okay, I just downloaded beta3, and it looks like that is the case now.
> problem with your example is that you are in fact trying to override a
> previous task definition, since there's already a <test> task in Ant.
> if that's the real name of your in-house task, you just need to name
> something else.

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

View raw message