Return-Path: Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 12952 invoked from network); 28 Feb 2001 01:22:13 -0000 Received: from web113.mail.yahoo.com (HELO web113.yahoomail.com) (205.180.60.84) by h31.sny.collab.net with SMTP; 28 Feb 2001 01:22:13 -0000 Received: (qmail 23496 invoked by uid 60001); 28 Feb 2001 01:22:17 -0000 Message-ID: <20010228012217.23495.qmail@web113.yahoomail.com> Received: from [207.76.204.131] by web113.yahoomail.com; Tue, 27 Feb 2001 17:22:17 PST Date: Tue, 27 Feb 2001 17:22:17 -0800 (PST) From: Diane Holt Subject: Re: ant task - property overrides To: ant-user@jakarta.apache.org In-Reply-To: <3A9BEFC2.2DD7E0A3@micromuse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N --- Juno Suk wrote: > The Ant task, called from a parent build.xml, will have all its > properties overridden by the parent. The task does allow you to set values for properties -- you just need to do it explicitly (which admittedly, could get fairly cumbersome if you have lots of properties you need to set). > Isn't this counterintuitive? Shouldn't properties > set within the subproject override its parent's properties? It's been a topic of discussion for awhile. I think the main stumbling block has been what to do about command-line defines. > Is there a quick way to workaround this problem? I'm trying to automate > build recursion through a hierarchy, but the fact that the parent > property overrides its children's frustrates me. The quickest way for now would be to pass the values explicitly in the task, since that's already available. Diane ===== (holtdl@yahoo.com) __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/