Return-Path: 
 <ant-dev-return-41600-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 41772 invoked from network); 23 Jan 2003 18:54:29 -0000
Received: from exchange.sun.com (192.18.33.10)
  by 208.185.179.12.available.above.net with SMTP; 23 Jan 2003 18:54:29 -0000
Received: (qmail 3017 invoked by uid 97); 23 Jan 2003 18:55:34 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 2706 invoked by uid 97); 23 Jan 2003 18:55:30 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-dev-help@jakarta.apache.org>
List-Post: <mailto:ant-dev@jakarta.apache.org>
List-Id: "Ant Developers List" <ant-dev.jakarta.apache.org>
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 2572 invoked by uid 98); 23 Jan 2003 18:55:29 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
X-Injected-Via-Gmane: http://gmane.org/
To: ant-dev@jakarta.apache.org
From: Costin Manolache <cmanolache@yahoo.com>
Subject: Re: Import basedir
Date: Thu, 23 Jan 2003 10:50:12 -0800
Lines: 52
Message-ID: <b0pdgr$rvt$1@main.gmane.org>
References: <b0mo1s$ah2$1@main.gmane.org> <m3of68gu68.fsf@bodewig.bost.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet@main.gmane.org
User-Agent: KNode/0.7.1
Sender: news <news@main.gmane.org>
X-Spam-Rating: 208.185.179.12.available.above.net 1.6.2 0/1000/N
X-Spam-Rating: 208.185.179.12.available.above.net 1.6.2 0/1000/N

Stefan Bodewig wrote:

> On Wed, 22 Jan 2003, Costin Manolache <cmanolache@yahoo.com> wrote:
> 
>> There are 2 intuitive behaviors:
>> - resolve a relative path based on the file where it was included
>> - resolve it based on some base dir ( like PWD on unix ).
>> 
>> Since most ant files are currently using the build file as base - I
>> think that must be the default, with explicit overrides permitted.
> 
> I'm not sure I understand what you mean.
> 
> All ant files use the build-file's basedir as base 8-) - if they don't
> specify a basedir attribute, this is implicitly set to the directory
> the build file is located in.  So to avoid confusion, the basedir
> attribute, if present, should be taken into account.

I know. That's the current behavior, and it needs to be supported:
- an explicit basedir in import
- the basedir attribute of <project>
- the location of the imported build file ).

What I'm trying to say is that "intuitive" ( IMHO ) is one of the 2 - 
relative to the location of the file where the relative path is found,
or relative to some global basedir. 

Pre-import, all relative locations where based on the location of the
file where they were used ( unless overriden by an explicit basedir )

If the default will be "single basedir ( of the importing file )" - then
we need a way to override this for older files. 
If the default will be "base on the basedir/location of the imported file" - 
then it is very easy to override with a basedir in import.

<import file="foo/bar.xml" basedir="foo" > will be used in the 
default is "importing file basedir", if we want to use bar.xml location

<import file="foo/bar.xml" basedir="${basedir}" > will be used if the 
default is "use imported file basedir" and we want to use change to use the 
importing basedir.

Or better <import file=.. useBaseDir="child|parent" />.

Costin




 




--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>