Return-Path: Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Delivered-To: mailing list dev@ant.apache.org Received: (qmail 58540 invoked from network); 1 Apr 2003 19:48:01 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 1 Apr 2003 19:48:01 -0000 Received: (qmail 14831 invoked by uid 50); 1 Apr 2003 19:49:53 -0000 Date: 1 Apr 2003 19:49:53 -0000 Message-ID: <20030401194953.14830.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@ant.apache.org Cc: Subject: DO NOT REPLY [Bug 18581] New: - ClearCase ChangeLog Task X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18581 ClearCase ChangeLog Task Summary: ClearCase ChangeLog Task Product: Ant Version: 1.1 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Optional Tasks AssignedTo: dev@ant.apache.org ReportedBy: vpertsov@cme.com I've written a clearcase change log task. The task allows companies using clearcase to easily generate a html log of changes between the current build and the prior build. The file can then be posted somewhere or emailed to QA team for appropriate regression testing. The task receives two labels. The idea is that each build should be labeled. This allows you to compare two labels for file versions present in one but not in the other. For each file, the task then retrieves the comments used to checkin the selected file. The result is an HTML document listing all the files changed between builds along with their comments. Vadim