From ant-dev-return-14089-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org Thu May 24 20:21:07 2001 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 38568 invoked by uid 500); 24 May 2001 20:21:07 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 38515 invoked from network); 24 May 2001 20:21:07 -0000 Message-ID: <8D82D0C76653D411834100508BC872A401664711@xs001sea.inside.sealabs.com> From: Whitney Hunter To: "'Ant Dev List'" Subject: Properties and the tag Date: Thu, 24 May 2001 13:20:55 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Got no response on the ant-users list. Perhaps this is a more appropriate place... -----Original Message----- From: Whitney Hunter Sent: Wednesday, May 23, 2001 11:05 AM To: 'Ant User List' Subject: Properties and the tag Is it just me or does anyone else think that it is bad that when the tag is used to execute a sub-build, the properties defined in the enclosing build file override the properties defined in an enclosed build file? I have a property that I define in all of my build files: "build_dir". I do not wish for this to be configurable, but I am forced to either make of of these property names unique or pass in the value from an embedded tag within the tag. This does not make sense to me. The semantics that I expected (and I think is best) is for the properties of enclosing file to be available in the enclosed unless they are defined in the enclosed file. If a property is redefined in an enclosed file, it should override the enclosing file. If you want to override an enclosed property from the enclosing file, then use the embedded property syntax for . This is way that environment variables work in various unix shells. Comments? Whitney