Return-Path: Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 64629 invoked by uid 500); 5 Aug 2003 07:27:26 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 64550 invoked from network); 5 Aug 2003 07:27:25 -0000 Received: from bodewig.bost.de (62.96.16.111) by daedalus.apache.org with SMTP; 5 Aug 2003 07:27:25 -0000 Received: (from bodewig@localhost) by bodewig.bost.de (8.11.6/8.11.6) id h757RY532261; Tue, 5 Aug 2003 09:27:34 +0200 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: user@ant.apache.org Subject: Re: question References: <7A57F750AF65D411949C00508BDFD8181DC6617A@USPLM202> From: Stefan Bodewig Date: 05 Aug 2003 09:27:34 +0200 In-Reply-To: <7A57F750AF65D411949C00508BDFD8181DC6617A@USPLM202> Message-ID: Lines: 66 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 4 Aug 2003, William Lopez wrote: > Why isn't the param value being "scoped"? I don't think I understand the question. creates a property that will only exist for the "subbuild" you've invoked with and that will be unset after . > I was under the impression that an encapsulates all the > properties associated with the target being called (unless > inheritAll="false") including any properties that were set in > depends target calls. Not sure what "encapsulate" means here, but it sounds correct. > What I noticed was that the > was not being set when the depends call to chk-ejbjndi-outofdate > target was executed. > > > > includes="**/*.class"/> > > > path="${app.module.dir}\${jndiPrefix}\${ejb.jar.name}"/> > > > ${jndiPrefix} notuptodate: ${jndi_outofdate} > > > if="jndi_outofdate"> > > > Let's see. When you invoke this as ant ejb.jar.prefix the following things happen: (1) chk-ejbjndi-outofdate will be run (as ejb.jar.prefix depends on it). (2) If the property jndi_outofdate has been set, the target ejb.jar.prefix will be executed. (3) Ant starts a fresh "subbuild" running ejb.jar. All properties that have been set at the point of will be set in this subbuild and have the same value. In addition there will be a property named jndiPrefix in the subbuild. As I don't see the ejb.jar target I cannot say whether it will be invoked directly or whether any other target gets executed first (those ejb.jar depends upon will be executed). I don't see why you expect jndiPrefix to be set while running chk-ejbjndi-outofdate. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org