ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sitsky <>
Subject Re: [PATCH] Suggestion for <ant> task
Date Tue, 16 Oct 2001 08:10:51 GMT
I am more than happy to work on this, but I guess I'd like to hear if this 
will be accepted or not, and what the preferred way of doing it would be.  

I think it would be useful to print out the depth, along with the build 
script and target name.


On Tuesday 16 October 2001 17:55, Jesse Glick wrote:
> David Sitsky wrote:
> > [snip]
> > The simple patch attached changes the <ant> task so that before
> > calling a target in another Project, it does a log() to indicate which
> > target and buildfile it is about to call, and the number of <ant>
> > nesting levels it is currently at.  It also does a log() when the
> > target called has completed. [snip]
> I know this would be extremely useful on my project, where there is one
> master build script and dozens of slave scripts, each of which has more
> or less the same target names.
> Two comments about the patch:
> - public changes to Project would not be necessary if kept a
> static thread-local variable for the nesting level (or it could use an
> undocumented property on the project)
> - it might be possible to do this entirely in the logger, not the <ant>
> task: you get targetStarted and targetFinished events which tell you
> which target and hence which project you are currently working on; could
> infer the depth from that, or simply print a message giving the new
> build script name whenever different from that of the last target
> -Jesse

View raw message