From ant-dev-return-30666-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org Sat Apr 20 08:05:48 2002 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 25918 invoked from network); 20 Apr 2002 08:05:48 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 20 Apr 2002 08:05:48 -0000 Received: (qmail 14002 invoked by uid 97); 20 Apr 2002 08:05:57 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 13980 invoked by uid 97); 20 Apr 2002 08:05:56 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 13969 invoked from network); 20 Apr 2002 08:05:56 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Adam Murdoch To: "Ant Developers List" Subject: Re: [myrmidon] CVS move Date: Sat, 20 Apr 2002 18:08:48 +1000 X-Mailer: KMail [version 1.4] References: <200204142137.42981.peter@apache.org> <200204162246.26261.adammurdoch@apache.org> <200204180751.11627.peter@apache.org> In-Reply-To: <200204180751.11627.peter@apache.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200204201808.48736.adammurdoch@apache.org> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, 18 Apr 2002 07:51, Peter Donald wrote: > > What is a workspace, exactly? > > a set of projects that reference each other and in which a common threa= d of > execution can travel through. ie So basically it is a graph of reachabl= e > nodes from root project. > > Currently it also contains the state of the execution in it aswell. Should it not? > > > > > goes to > > > > > > This is an interesting idea. Do we want to go with something like this? = (I=20 reckon we should). Would it work something like: - Executes target A in the same execution frame as the calling target. - Only executes target A if it has not already been executed in this exec= ution=20 frame. =20 - Allows the "project->target" syntax for referencing targets in other=20 projects. - Allows property resolution in the name attribute. - Would fail if there is a cycle in the calls. - It would not allow properties to be specified. > This supports all of the functionality that people have been asking for= =2E > But it means a "magic" task name (or a magic task). No more magic than, say, or . Let's make it a task, as it= =20 should fall out of whatever 'execute-a-target' service we come up with fo= r=20 and . And that means it will be available as a nested tas= k in=20 , and so on. That would also be pretty much the last of the declarative stuff gone too= ,=20 which wouldn't be a bad thing (now we can have scripty tasks :) --=20 Adam -- To unsubscribe, e-mail: For additional commands, e-mail: