Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 86828 invoked by uid 500); 21 Mar 2001 22:38:23 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 86790 invoked from network); 21 Mar 2001 22:38:23 -0000 Content-return: allowed Date: Wed, 21 Mar 2001 14:37:59 -0800 From: David Martinez Subject: RE: Mozilla-style VersionBlame? To: "'ant-user@jakarta.apache.org'" Message-id: <55B75BC35F1AD1499ACF45A9EEB069867D2AA5@essfo01.ad.food.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: multipart/alternative; boundary="----_=_NextPart_001_01C0B257.94BBF978" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0B257.94BBF978 Content-Type: text/plain; charset="iso-8859-1" Well, at risk of restarting the debate (lowering my head as I say this to avoid flying assorted fruit), they actually don't have to be unified at all. They just need to implement a common interface, should they decide to do so (which would be limited in this case to who check in file XX last). In lieu of that they could also be wrapped by something that does implement the interface. Just my 1c -----Original Message----- From: Nick Christopher [mailto:nwc@visionics.com] Sent: Wednesday, March 21, 2001 12:14 PM To: ant-user@jakarta.apache.org Subject: Re: Mozilla-style VersionBlame? David Martinez wrote: If there is a compile error that breaks the build, query the version control system (the different version control tasks ant already has should implement some sort of unified interface for this purpose) for the name & email address of the last check-in on the files that broke. There's the rub, unified version control tasks have been hotly debated and are currently out of favor. ------_=_NextPart_001_01C0B257.94BBF978 Content-Type: text/html; charset="iso-8859-1"
Well, at risk of restarting the debate (lowering my head as I say this to avoid flying assorted fruit), they actually don't have to be unified at all. They just need to implement a common interface, should they decide to do so (which would be limited in this case to who check in file XX last). In lieu of that they could also be wrapped by something that does implement the interface.
 
Just my 1c
-----Original Message-----
From: Nick Christopher [mailto:nwc@visionics.com]
Sent: Wednesday, March 21, 2001 12:14 PM
To: ant-user@jakarta.apache.org
Subject: Re: Mozilla-style VersionBlame?

David Martinez wrote:
 

If there is a compile error that breaks the build, query the version control system (the different version control tasks ant already has should implement some sort of unified interface for this purpose) for the name & email address of the last check-in on the files that broke.
 


There's the rub, unified version control tasks have been hotly debated and are currently out of favor.
 

------_=_NextPart_001_01C0B257.94BBF978--