Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 48532 invoked by uid 500); 22 Oct 2001 03:57:23 -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 48523 invoked from network); 22 Oct 2001 03:57:22 -0000 Message-ID: <3BD3992B.4090700@arielpartners.com> Date: Sun, 21 Oct 2001 23:57:31 -0400 From: "Craeg K. Strong" Organization: Ariel Partners LLC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012 X-Accept-Language: en-us MIME-Version: 1.0 To: ant-dev@jakarta.apache.org Subject: Re: [PATCH] basedir for child project not set correctly from task References: <01102001454804.01081@localhost.localdomain> <3BD147EB.BF3A80D1@sun.com> <01102118024300.01087@localhost.localdomain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N David Sitsky wrote: >>As far as I can tell, there is no way to do the thing which I at least >>would 95% of the time want to do: run a specific build script and ask Ant >>to give it the basedir it specifies for itself (without hardcoding this >>into the calling script). >> >I would have thought this is what most users would be wanting too. For all >of my own "nested" buildfiles, I had basedir="." and always called them >using the "dir" attribute in the task. I didn't realise basedir in the >nested task is ignored in this circumstance (my fault for not reading the >manual properly). > Gentlemen: I submitted a patch a few weeks back to address this problem. It makes the task not override the child antfile basedir IFF inheritAll == false and no dir attribute specified. Please see: http://www.mail-archive.com/ant-dev%40jakarta.apache.org/msg10183.html I am guessing it may have been overlooked b/c a) the need to get 1.4.1 out the door b) one might argue it represents "new" ("changed") functionality Submitters: please consider this another request to commit this (tiny) patch, now that 1.4.1 has shipped. Thanks! --Craeg