Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Message-Id: <200002240414.WAA12001@smtp.networkusa.net>
Date: Wed, 23 Feb 2000 21:59:32 -0600
To: ant-dev@jakarta.apache.org
From: Erik Meade <emeade@geekfarm.org>
Subject: Re: Proposal: XML output from ant tasks
In-Reply-To: <Pine.LNX.4.10.10002231147160.5006-100000@costin.eng.sun.co
 m>
References: <Pine.LNX.4.10.10002231105160.5006-100000@costin.eng.sun.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Yes.  This is just the kind of stuff I would like to be able to log so I
can generate some measurements for myself.  I was just planning
on parsing it out from a file, xml would help there!

Erik Meade

At 11:54 AM 2/23/00 -0800, you wrote:
>Hi,
>
>Right now ant has a very nice file format and works great, but if you
>build a large project you'll probably get a lot of messages - some of them
>are warnings ( deprecated methods ), some are important info ( time to
>build, non-critical failures ).
>
>Also, with conditional compilation we will have some very important
>messages describing what was actualy build into the dist.
>
>The problem is that it takes time to extract the information, and it is
>hard to automate it. 
>
>One possible solution is ( guess what? ) xml. If we convert all logs to
>display well-formed XML it will be easy to post-process the results 
>and even have a nice format.
>
>The price is not big - the output will still be readable.  It can be an
>incremental job, with log() changed to wrap everything in a generic
><log:ant > tag with the source and level, and then we can add format to
>the most important messages ( like deprecations, not-fatal warnings,
>conditional compilations, etc).
>
>What do you think? 
>
>Costin  
>