Return-Path: 
 <ant-dev-return-16965-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org
Received: (qmail 13825 invoked by uid 500); 20 Aug 2001 13:07:30 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
list-help: <mailto:ant-dev-help@jakarta.apache.org>
list-unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
list-post: <mailto:ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 13816 invoked from network); 20 Aug 2001 13:07:30 -0000
Message-ID: <9B3E950CB293D411ADF4009027B0A4D2020143F5@maileu.imediation.com>
From: Stephane Bailliez <sbailliez@imediation.com>
To: ant-dev@jakarta.apache.org
Subject: <ant> task
Date: Mon, 20 Aug 2001 14:09:50 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N


I need some explanation about <ant> task and the recent introduction of
inheritall.

It looks like to me that it prevents the called ant file to define its
basedir whether or not inheritall is true/false. Therefore all =
definitions
that occurs inside the build file are based on the parent basedir and =
not
the called one.

I always have:
"Override ignored for user property basedir"

Is that the defined behavior ?

It would have been useful so that I can set an external repository of
properties and path that are resolved relative to the called file. =
Though
I'm walking a little bit on 'build include' side :)

--=20
 St=E9phane Bailliez=20
 Software Engineer, Paris - France=20
 iMediation - http://www.imediation.com=20
 Disclaimer: All the opinions expressed above are mine and not those =
from my
company.=20