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 83966 invoked from network); 23 May 2000 11:07:41 -0000 Received: from hermes.ext.eurgw.xerox.com (HELO hermes.eurgw.xerox.com) (212.120.143.5) by locus.apache.org with SMTP; 23 May 2000 11:07:41 -0000 Received: from eurodns4.eur.xerox.com (eurodns4.eur.xerox.com [13.202.66.50]) by hermes.eurgw.xerox.com (8.9.3/8.9.3) with ESMTP id MAA04160 for ; Tue, 23 May 2000 12:06:59 +0100 (BST) Received: from eurgbrmg01.eur.xerox.com by eurodns4.eur.xerox.com (8.9.3/SMI-4.1) id KAA21903; Tue, 23 May 2000 10:49:25 +0100 (BST) Received: from eurgbrbh01.emeacinops.xerox.com (unverified) by eurgbrmg01.eur.xerox.com (Content Technologies SMTPRS 4.1.5) with ESMTP id for ; Tue, 23 May 2000 10:49:24 +0100 Received: by eurgbrbh01.emeacinops.xerox.com with Internet Mail Service (5.5.2448.0) id ; Tue, 23 May 2000 10:42:02 +0100 Message-ID: <5158BC6D771ED3118D6200508B2C272219BBBB@gbrxmsms01.bh.gbr.xerox.com> From: "Everitt, Andrew" To: "'ant-dev@jakarta.apache.org'" Subject: RE: Call for patches Date: Tue, 23 May 2000 10:49:41 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Sam, I have two things which might be of interest: * 'Modern compile' implementation (not written by me, I used something that was posted here a couple of weeks ago!). I have at least 3 of our developers using this and it seems to work OK :-). * A first stab at a taskdef for interacting with Microsoft Visual SourceSafe. It only supports 'get' from SourceSafe at the moment but should be extensible. If you are interested then mail me! Cheers, Andi. ____________________ Andrew Everitt Xerox Mobile Solutions, Cambridge. UK -----Original Message----- From: rubys@us.ibm.com [mailto:rubys@us.ibm.com] Sent: 23 May 2000 03:33 To: ant-dev@jakarta.apache.org Subject: Call for patches .duncan wrote: >Probably too early in the game. In the requirements doc, there's a start >at talking about how this could be done. We need to have consensus on >that and implementation of course. It is hard to achieve consensus when we never seem to even have a quorum. Yes, Duncan, I'm talking about you. And me, lately, for that matter. Due to the recent security breach, it is difficult to get new committers. And the same breach contributed to the downfall of the only tracking system we have had to date - Bugzilla. Over the next few weeks, I am going to try to commit a bunch of changes. I'm going to look at my personal archives for this mailing list, but quite frankly if you have something that you want added, the way to increase your changes is to post it again. Now. Things I'll be looking for: 1) bug fixes. Things obviously broken. 2) consistency. Task A calls one thing bar, Task B calls a similar thing baz. 3) extensibility, maintainability enhancements for taskdef writers. Unless it is a clear simplification, I am *not* looking for changes to build.xml files at this time. 4) new, independent, tasks. Preferably, something that does something novel or different. Ones that do *not* require changes to the "core" of Ant. 5) cleanup. Deprecated items, for example, should ultimately be removed. Once the ability to get new committers opens up a bit, I plan to propose a few. Yes, I could propose committers now, but I couldn't tell you when they would be effective. Furthermore, I have other things in the queue for the people with root access that - yes, a bit selfishly - I would like to see done first. People I will be looking for are people with perseverance And with opinions. And not necessarily ones I agree with. It will take more than a few sparks to keep this flame lit. - Sam Ruby P.S. Please send the patches here, and not directly to me.