Return-Path: Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 66039 invoked by uid 500); 25 Jul 2003 15:17:39 -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 66026 invoked from network); 25 Jul 2003 15:17:39 -0000 Received: from main.gmane.org (80.91.224.249) by daedalus.apache.org with SMTP; 25 Jul 2003 15:17:39 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19g4Ix-00026x-00 for ; Fri, 25 Jul 2003 17:16:23 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: dev@ant.apache.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19g4Ix-00026o-00 for ; Fri, 25 Jul 2003 17:16:23 +0200 From: Nicola Ken Barozzi Subject: Re: ant 1.5.4 : Import Date: Fri, 25 Jul 2003 17:15:51 +0200 Lines: 83 Message-ID: References: <9D2C6E61BF2E484A98AAC680695EDA6E07125593@us1ex1.corp.e2open.com> <200307260051.36167.conor@cortexebusiness.com.au> <200307260119.16744.conor@cortexebusiness.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en In-Reply-To: <200307260119.16744.conor@cortexebusiness.com.au> Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Conor MacNeill wrote, On 25/07/2003 17.19: > On Sat, 26 Jul 2003 12:52 am, Stefan Bodewig wrote: > >>On Sat, 26 Jul 2003, Conor MacNeill >> >>wrote: >> >>>Clear as mud? >> >>Errm, yes. >> >>How would you do >> >> >> >> >> >> >> >>?? >> >>By not using relative paths (but something like ${this.basedir}/lib), >>I guess. > > > Good question. Currently you get a property telling you the location of your > build file - not your basedir. Correct, bacause the basedir has no meaning as the file is imported. What about ant.projectdir and ant.projectdir.projectname properties? > BTW, the property is based on the project's name which might be an issue if > the name is controllable by the importing build file. Is a name mandatory for > an importable project or just one that want to know its location? IMHO the latter. Explaining a bit more my cases: 1) I have a project that is made only to be imported: ... - Ant will deny the use of it standalone - I would need this when I use the ant.file.currentproject property that is not available when I run it standalone. (although we could as well put it, and so this use-case looses meaning it seems) 2) I have a project that is not made to be imported: ... - Ant will deny the use of it as imported - This project does not check that the resources and paths are resolved using the ant.file.projectname property, and thus would not work properly if imported. In this case the name attribute is mandatory. 3) I have a project that can be imported or used as-is: ... - Ant will never deny it's use - This project does not use external resources, or checks for them in a manner that works in both scenarios. 4) I have a project that does not say if it can be imported: ... - Ant will never deny it's use but warn if it's imported - The author does not tell you how it's meant to use. Most probably it's not made to be imported, so if you want to import it, good luck! -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org