Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 80697 invoked by uid 500); 8 May 2001 13:24:14 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 80237 invoked from network); 8 May 2001 13:23:40 -0000 Message-Id: <3.0.6.32.20010508230215.01e6fe20@mail.alphalink.com.au> X-Sender: gdonald@mail.alphalink.com.au X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 08 May 2001 23:02:15 +1000 To: ant-dev@jakarta.apache.org From: Peter Donald Subject: [Vote] Interfaces for Project/Target Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hi, I would like to see what people think about using interfaces for Project/Target. As the contract between project-engine and projects is fairly clear-cut and precise (ie project contains targets, targets contain task proxies) it is simple to specify a minimal interface between the two and a simple implementation. (see myrmidon proposal for an example). The advantages for doing it this way are mainly for the integrators. It would be extremely easy to reimplement the interface so that it could sit in a swing treelist or someother GUI integration. I can't see what we loose from it but we make it much easier for people who want to build things like antidote. Vote/Thoughts? Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*