Return-Path: Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 14952 invoked by uid 500); 24 Jul 2003 23:25:14 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 14937 invoked from network); 24 Jul 2003 23:25:13 -0000 Received: from cortex-gw.magna.com.au (HELO smtp.cortexebusiness.com.au) (203.174.140.214) by daedalus.apache.org with SMTP; 24 Jul 2003 23:25:13 -0000 Received: (from daemon@localhost) by smtp.cortexebusiness.com.au (8.10.0/8.10.0) id h6ONPGp05623 for ; Fri, 25 Jul 2003 09:25:16 +1000 (EST) Received: from UNKNOWN(192.168.1.9), claiming to be "chunky.int.cortexebusiness.com.au" via SMTP by ctx00, id smtpdAAASzay7k; Fri Jul 25 09:25:10 2003 Received: (from daemon@localhost) by chunky.int.cortexebusiness.com.au (8.10.0/8.10.0) id h6ONPEb12143 for ; Fri, 25 Jul 2003 09:25:14 +1000 (EST) Received: from UNKNOWN(192.168.1.48), claiming to be "kooky.int.cortexebusiness.com.au" via SMTP by chunky, id smtpdAAACuayex; Fri Jul 25 09:25:06 2003 From: Conor MacNeill To: "Ant Developers List" Subject: Re: ant 1.5.4 : Import Date: Fri, 25 Jul 2003 09:25:05 +1000 User-Agent: KMail/1.5 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307250925.05891.conor@cortexebusiness.com.au> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 25 Jul 2003 01:50 am, Dominique Devienne wrote: > Getting back to your point, where does that leaves us for basedir? > I've slept on it :-). I'd vote to go with the current behaviour. i.e. ignore basedir. Import tasks will always import relative to the file containing the import statement. Slightly different from the standard Ant file resolution behaviour but a reasonable approach for . In the end, since most people use "." for basedir, it would not be a problem in general. If you want to be able to build files to only function as imports, I'd support that (so called dual behaviour). In fact, I'd be tempted to use an element besides to make it even more explicit. Such an element would not support basedir. I did that in Mutant - it was called but it could be called . I wouldn't find that confusing with the task but others might - maybe So +1 on capability to restrict a build file to only be ed -1 to make that mandatory for s +0 to an attribute in project to designate such files +1 to a new root element instead. Thoughts? Conor --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org