ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antoine Levy-Lambert" <>
Subject Re: Logging/run-time info best practices? [WAS: RE: environment variable]
Date Thu, 31 Jul 2003 11:02:52 GMT

----- Original Message -----
From: "Svetlin Stanchev" <>
Sent: Thursday, July 31, 2003 12:40 PM

> OK, then my question would be rather:
> "What are the best practices for different build user groups like
> developers, support, release managers or simply for debug output?"
> How does one control the amount of outputed build run info on the screen
> with Ant means (preferably avoiding using outside settings, like
> environment, wrappers, or command-line options)?

With ant (without programming) you cannot control how much output is
You can just choose between starting ant with the default logging level, or
ant -verbose
ant -debug
If you want to write your own GUI in Java to start ant, you could for
instance add 3 listeners to to the build (classes implementing
BuildListener), one of them listening to the MSG_INFO level, the second one
to VERBOSE level, the 3d to DEBUG level, and present the output in 3 frames
or in a tabbed control if something like that is available.
Or you could just have one logger and store the output together with the
message priorities in an array of objects, then display the messages with
some kind of collapsable tree structure, where by default you would only see
the INFO and ERR message, and clicking to expand branches of the tree would
show the VERBOSE, then the DEBUG messages.
That's all I can think of.

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

View raw message