ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay Glanville" <>
Subject [SUBMIT] New task: recorder
Date Wed, 28 Mar 2001 14:02:01 GMT
I am submitting (for everyone's pleasure) a new task, called <recorder>.

The recorder task allows a user to state a log file inside the build.xml
file.  Feature of the recorder are setting (and modifying on the fly) the
logging level to record, and manual starting and stopping of the recording.

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.

There are two new classes to go into the ant.taskdef package (
and, and a new document to go into the manual/coretasks
(recorder.html).  The in the taskdef directory also
needs to be modified (to add the new task) and according to CVS, the diff
  cvs diff (in directory
  RCS file:
  retrieving revision 1.64
  diff -r1.64

So, please use this task and send me feedback on how useful it is, what
could work better, what features you want in the future, etc.


You know, I'm surprised that no one has added a diff target to ant's
build.xml source version that goes through the entire CVS tree looking for
things that have been modified, performs diffs on all these files and
records them to a log file.  This way, coders simply need to do a "build
diff" command to see a capturing of all their work.  Then, the submitters
can simply do a "build patch" command (the patch target would also need to
be created) to update CVS.  Of course, this is just me spouting off of the
top of my head - I haven't' thought of any of the implementation details, or
possible pitfalls.  Wouldn't such targets be deemed useful?


Jay Dickon Glanville
P068 - SiteManager Development, Nortel Networks
613-765-1144 (ESN 395-1144)
MS: 045/55/A05

 <<recorder.html>>  <<>>  <<>>

View raw message