Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 61440 invoked from network); 10 Dec 2009 05:12:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Dec 2009 05:12:00 -0000 Received: (qmail 7070 invoked by uid 500); 10 Dec 2009 05:12:00 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 6907 invoked by uid 500); 10 Dec 2009 05:11:59 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 6897 invoked by uid 99); 10 Dec 2009 05:11:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2009 05:11:59 +0000 X-ASF-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [88.84.128.168] (HELO samaflost.de) (88.84.128.168) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2009 05:11:57 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by samaflost.de (Postfix) with ESMTP id A7480289801B for ; Thu, 10 Dec 2009 06:11:35 +0100 (CET) Received: from samaflost.de ([127.0.0.1]) by localhost (v35516.1blu.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1TBQXseAajmv for ; Thu, 10 Dec 2009 06:11:35 +0100 (CET) Received: by samaflost.de (Postfix, from userid 1000) id D902A289801D; Thu, 10 Dec 2009 06:11:34 +0100 (CET) From: Stefan Bodewig To: dev@ant.apache.org Subject: target-group in trunk X-Draft-From: ("nnfolder:mail.jakarta-ant") Date: Thu, 10 Dec 2009 06:11:34 +0100 Message-ID: <874onzs9a1.fsf@v35516.1blu.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hi, this is just a description of what target-group in trunk currently is and what it is not. I'll describe the implementation rather than the initial phase concept as it is implemented in EasyAnt which uses a custom ProjectHelper to implement its slightly different concept. This mail serves as background in addition to the thread Nicolas has started. A target-group is basically a target with two differences: * must be empty * its depends list can be added to during parse time. Other targets and target-groups can declare themselves as part of the group and get added to the group's depends list. That's all. Order of execution is still only determined by the depends attributes of all targets. For anybody running a build target-groups are just like targets. They are listed together with targets in -projecthelp and create BuildEvents and log output of targets. A target-group is not a container of targets. It doesn't provide a grouping in a sense that a target would be executed as part of a group - the depends lists of all targets and target-groups still determine the order. Since a target-group is always empty, the if and unless attributes don't have any effect at all. Of course we could change the implementation to get to a more composite-like implementation - making if and unless useful and maybe introduce new build events - it is just not clear (to me) whether the additional effort would provide anything more useful. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org