Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
To: dev@ant.apache.org
Subject: Re: ant 1.5.4 : Import
References: <747F247264ECE34CA60E323FEF0CCC0C0F5116@london.cellectivity.com>
	<200307290923.54205.conor@cortexebusiness.com.au>
From: Stefan Bodewig <bodewig@apache.org>
Date: 29 Jul 2003 12:59:57 +0200
In-Reply-To: <200307290923.54205.conor@cortexebusiness.com.au>
Message-ID: <m3smopmwcy.fsf@bodewig.bost.de>
Lines: 23
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

If you want to simplify things, why not go even further?

On Tue, 29 Jul 2003, Conor MacNeill <conor@cortexebusiness.com.au>
wrote:

> 1. import with optional name. The name is to be used in the renaming
> of targets.

I'd like to think about removing target renaming completely.  What
exactly is the use-case for this?  I've come up with a vague idea, but
it would help tremendously what people do want this feature for.

> 2. Define a single property ant.import.file which is resolved at
> import time to the import location. All other properties are nt
> resolved.

Why does the imported/included file need to know its name, after we've
limited it to not access resources relative to its own basedir as in

> 4. All normal Ant operations (i.e. not imports) are resolved to the
> basedir of the outer project. There is no access to other basedirs.

Stefan

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