From james.davidson@eng.sun.com Fri Feb 25 01:26:55 2000 Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 44467 invoked from network); 25 Feb 2000 01:26:55 -0000 Received: from mercury.sun.com (192.9.25.1) by locus.apache.org with SMTP; 25 Feb 2000 01:26:55 -0000 Received: from shorter.eng.sun.com ([129.144.252.35]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA01933 for ; Thu, 24 Feb 2000 17:26:54 -0800 (PST) Received: from ionic (d-ucup02-124-65 [129.144.124.65]) by shorter.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with SMTP id RAA28795 for ; Thu, 24 Feb 2000 17:26:53 -0800 (PST) Message-ID: <019e01bf7f2f$853cad80$417c9081@ionic> From: "James Duncan Davidson" To: References: Subject: Re: Proposal: XML output from ant tasks Date: Thu, 24 Feb 2000 17:27:46 -0800 Organization: Sun Microsystems, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 > The end goal is not to reduce clutter, but to allow post-processing. Ah. Got it. So let me make a counter proposal -- .log(String msg) goes to an XML based .log file .message(String msg) goes to the console This lets human readable messages go to the console and machine readable messages go to a log file. This lets the task do a few things 1) reduce the amount of clutter sent to the console 2) give a "Stopping because of fatal error, see log" type message The .log file should be very verbose to give the kind of info that you want in post-processing nightly builds, etc -- and because of this, the console messages can get tighter. How's that sound? .duncan