From ant-dev-return-26513-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org Tue Feb 26 16:58:38 2002 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 84799 invoked from network); 26 Feb 2002 16:58:37 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Feb 2002 16:58:37 -0000 Received: (qmail 5864 invoked by uid 97); 26 Feb 2002 16:58:36 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 5747 invoked by uid 97); 26 Feb 2002 16:58:35 -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 5736 invoked from network); 26 Feb 2002 16:58:35 -0000 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: ant-dev@jakarta.apache.org Subject: Re: Ids from paths not propogated through antcalls unless path is top-level References: <20020224140240.65846.qmail@apache.org> <00b501c1bd40$5cd0f800$d1eefea9@homenkf0y0hwu0> <001501c1bd44$76d1c7d0$6601a8c0@darden.virginia.edu> <00d301c1bd49$b157ad20$d1eefea9@homenkf0y0hwu0> <007001c1bd61$7c8fc9c0$1502a8c0@Stelvio> <3C7952F2.4020908@exis.com> <017b01c1bda7$49d4b770$1502a8c0@Stelvio> <3C7A6F9B.2010106@exis.com> From: Stefan Bodewig Date: 26 Feb 2002 17:43:38 +0100 In-Reply-To: <3C7A6F9B.2010106@exis.com> Message-ID: Lines: 23 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Civil Service) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 Mon, 25 Feb 2002, Colin Sampaleanu wrote: > If I don't do this, then what effectively happens is that if I have > multiple targets in the dependency chain which say they depende on > init, as well as some other target, init will be called multiple > times, No. If all you have are depends attributes on targets and no or tasks are involved, every target will be executed at most once per build. Where ant A B counts as two builds, just to clarify. If you see some different behavior, you've found a bug - and we'd like to have a testcase to reproduce it, of course 8-). > if antcall also lost properties, does - and it has been added in Ant 1.4. Stefan -- To unsubscribe, e-mail: For additional commands, e-mail: