Return-Path: 
 <ant-user-return-6111-apmail-jakarta-ant-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org
Received: (qmail 1921 invoked by uid 500); 28 Mar 2001 16:37:17 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
Reply-To: ant-user@jakarta.apache.org
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 1910 invoked from network); 28 Mar 2001 16:37:16 -0000
Message-ID: <6DDA62170439D31185750000F80826AC05A2FC22@zmerd004.ca.nortel.com>
From: "Jay Glanville" <dickon@nortelnetworks.com>
To: "Ant-User (text)" <ant-user@jakarta.apache.org>
Subject: RE: New Task: Recorder. Feedback requested.
Date: Wed, 28 Mar 2001 11:36:22 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Orig: <dickon@americasm01.nt.com>
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

feedback ... love feedback ...

> -----Original Message-----
> From: KC Baltz [mailto:KBaltz@responsenetworks.com]
> 
> What is the default logging level?  The docs say that omitting this
> parameter will cause no change, but what's it set to initially?

The default is the same as the default for Ant: info.  Unfortunately, the
project doesn't know what the current logging level is (as stated by the
command line) therefore, if the user says "-verbose" on the command line,
<recorder> doesn't see that.  I hope to solve that in the future.  As for
the documentation, good point.  I'll try to update the HTML with default.

> Also, s/coma/comma/g  :)

he ... he ... he ... opps.

> I'll try it here.  It sounds helpful for sending out emails.  
> Is there a
> provision for closing the recorder?  

Not currently.  The print stream is flushed and closed on a BuildFinished
event.  Do you think that it should flush on every task completion, target
completion or every messaged logged?  Do you think that there should be a
task action to close the recorder (i.e.: <recorder file="${filename}"
action="close" />) where this would force the closure of the print stream?

> Is this necessary?  How 
> often does it
> "flush"?  I assume it will catch a build as it fails.  Also, 
> I would suggest
> that it should be failsafe by default.  In other words, if 
> something goes
> wrong with recorder, by default it shouldn't fail the build.  But a
> failOnError flag might be useful in that case.

The failOnError is a good idea.  I'll add that one to the core functionality
list.

> K.C.
> 
> > -----Original Message-----
> > From: Jay Glanville [mailto:dickon@nortelnetworks.com]
> > Sent: Wednesday, March 28, 2001 9:15 AM
> > To: Ant-User (text)
> > Subject: New Task: Recorder. Feedback requested.
> > 
> > 
> > I have created a new task that I'd like to get some feedback 
> > on.  Basically,
> > the <recorder> task allows logging control within the build.xml file
> > (currently, logging is only supported on the command line).
> > 
> > I have attached the necessary java files and an HTML file 
> > that documents how
> > to use the task.
> > 
> > I consider this to be of 0.5 level.  In other words, the basic core
> > functionality works and is tested, but I want feedback from 
> > users on all
> > aspects of functionality: core and future possibilities.
> > 
> > I have just submitted this code to the dev mailing list, 
> but I'm also
> > submitting it here in the hopes of getting more feedback.
> > 
> > In order to use it with ant 1.3, you need to use the 
> <taskdef> task to
> > declare the task:
> >   <taskdef name="recorder" 
> > classname="org.apache.tools.ant.taskdefs" />
> > and then use it in the way described in the attached html file.
> > 
> > So, let me know what you think.
> > 
> > Jay