Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 54924 invoked from network); 25 Feb 2002 02:51:05 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 Feb 2002 02:51:05 -0000 Received: (qmail 9719 invoked by uid 97); 25 Feb 2002 02:51:09 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 9698 invoked by uid 97); 25 Feb 2002 02:51:09 -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 9686 invoked from network); 25 Feb 2002 02:51:08 -0000 Message-ID: <017b01c1bda7$49d4b770$1502a8c0@Stelvio> From: "Steve Loughran" To: "Ant Developers List" 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> Subject: Re: Ids from paths not propogated through antcalls unless path is top-level Date: Sun, 24 Feb 2002 18:51:13 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Colin Sampaleanu" To: "Ant Developers List" Sent: Sunday, February 24, 2002 12:54 PM Subject: bug: Ids from paths not propogated through antcalls unless path is top-level > Unless I am missing something, there is a bug in Ant 1.4.1 in that ids > from path structures don't propogate (aren't usable) through antcalls, > unless the path structure defining the id is top level. Consider the > following ant script: actually, toplevel defs arent propagating through antcall either; they are being re-evaluated when the called target runs >A target should >not know whether it is being called as a dependency or through an >antcall, and I do have a number that are executed both ways then it should state in its dependencies which targets it depends on to init paths and things. NB, now has inheritRefs; it seems that antcall should acquire the same attribute and pass it on to the ant task it uses to do its work. Colin, if you were to add that (and the tests to verify it works), then your problems will be solved. -- To unsubscribe, e-mail: For additional commands, e-mail: