Return-Path: Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 62818 invoked by uid 500); 4 Aug 2003 20:25:10 -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 62767 invoked from network); 4 Aug 2003 20:25:10 -0000 Received: from plmler5.mail.eds.com (199.228.142.70) by daedalus.apache.org with SMTP; 4 Aug 2003 20:25:10 -0000 Received: from plmlir3.mail.eds.com (plmlir3-2.mail.eds.com [199.228.142.133]) by plmler5.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h74KPFH20897 for ; Mon, 4 Aug 2003 15:25:15 -0500 Received: from plmlir3.mail.eds.com (localhost [127.0.0.1]) by plmlir3.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h74KPEF17259 for ; Mon, 4 Aug 2003 15:25:14 -0500 (CDT) Received: from usplm102.exsc01.exch.eds.com (USPLM102.txpln.us.eds.com [198.132.135.15]) by plmlir3.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h74KPEP17250 for ; Mon, 4 Aug 2003 15:25:14 -0500 (CDT) Received: by USPLM102.txpln.us.eds.com with Internet Mail Service (5.5.2656.59) id ; Mon, 4 Aug 2003 15:25:10 -0500 Message-ID: <7A57F750AF65D411949C00508BDFD8181DD157A4@USPLM202> From: "Lopez, William" To: Ant Users List Subject: RE: question Date: Mon, 4 Aug 2003 15:25:08 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Previously I had asked about a workaround for bug #11418 and I believe I found my answer, I will have to add 3 more targets to compensate- that's a shame. I looked at the tag and believe I will run into the same problem. If anyone else has a solution I'd like to hear from you. Thanks, -Will -----Original Message----- From: Shackelford, John-Mason [mailto:john-mason.shackelford@pearson.com] Sent: Monday, August 04, 2003 2:15 PM To: 'Ant Users List' Subject: RE: question William, I haven't read your email too carefully, but it might be worth looking at bug #11418 to see if you've been bit. John-Mason Shackelford Software Developer Pearson Educational Measurement - eMeasurement Group 2510 North Dodge St. Iowa City, IA 52245 ph. 319-354-9200x6214 john-mason.shackelford@pearson.com http://etest.ncspearson.com -----Original Message----- From: Lopez, William [mailto:william.lopez@eds.com] Sent: Monday, August 04, 2003 1:48 PM To: Ant Users List Subject: question Why isn't the param value being "scoped"? 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. I've tried several different ways to get the build logic to flow a certain way but each iteration (after failing to achieve desired results) becomes more of a hack (and messy)...this way appeared to be the cleanest way but it doesn't work as planned. What I noticed was that the was not being set when the depends call to chk-ejbjndi-outofdate target was executed. This compounds my confusion, how does the task execute when the ${jndiPrefix} property is not resolved? I know this because of the debug output: chk-ejbjndi-outofdate: Property ${jndiPrefix} has not been set The chain of events starts at the generate.ejb.jars target. Any insight will be greatly appreciated. ${jndiPrefix} notuptodate: ${jndi_outofdate} ... Thanks -----Original Message----- From: Lopez, William Sent: Thursday, July 31, 2003 12:04 AM To: 'Ant Users List' Subject: Conditional (compound) Help Please I have a need for a task that compares a jar to it's "list" of class files (found uptodate to work fine for the first part of the compare). I expect the second compare to never be true when the first is (*to meet the target execute condition*). The part is not working like I thought (as a negator)...I tried the task but it always ends up executing the target...see below, 2nd example. My scenario: -There is another task that executes unless="noprefix_uptodate"....this generates/deploys the ejb jar for the non-jndi prefix ejb -Then ejb.jar is called (via 3x - 1 per other jndi prefixes)...the only difference between these jars is the jndi prefix I'm sure there is a clean, simpler way but I can not figure it out. Thanks! ${jndiPrefix} notuptodate: ${jndi_property} ... ==================== ============================== ${jndiPrefix} notuptodate: ${jndi_outofdate} ... --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. **************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org