Return-Path: 
 <ant-dev-return-17608-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org
Received: (qmail 28478 invoked by uid 500); 12 Sep 2001 17:19:42 -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 28467 invoked from network); 12 Sep 2001 17:19:42 -0000
Content-Type: text/plain;
  charset="iso-8859-1"
From: Peter Donald <donaldp@apache.org>
To: ant-dev@jakarta.apache.org
Subject: Re: [PATCH] Added "ant.target.name" property
Date: Thu, 13 Sep 2001 03:09:51 +1000
X-Mailer: KMail [version 1.3.1]
References: 
 <BD05B730744DDFBAC1256AC50057532F.005753A1C1256AC5@opoipi.bancaintesa.it>
 <20010912165408.CCPB4715.mss.rdc2.nsw.optushome.com.au@there>
 <3B9F957B.4020603@liberate.com>
In-Reply-To: <3B9F957B.4020603@liberate.com>
X-Wisdom-Cookie: .
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <20010912171939.CLLH4715.mss.rdc2.nsw.optushome.com.au@there>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Thu, 13 Sep 2001 03:03, Peter Janes wrote:
> Peter Donald wrote:
> > So instead of
> >
> > <project name="foo" default="..." >
> >
> > you would have
> >
> > <project default="..." >
> >   <property name="name" value="foo" />
> >
> > And that works fine ;) Instead of name you could even use
> > ant.project.name as name of property and have it fully compatible ;)
>
> So why bother naming projects,

I don't and nor do any I get my hands on ;)

> then, if the name can't actually be used
> anywhere?  Or is that your point?

I am not sure I follow you. The name attribute of project is just a 
special-case property. My opinion is that it should be handled like every 
other property.

> Isn't staying out of the ant.* namespace, especially in user files, a Good
> Thing?  Sure, it's not explicitly forbidden, but since we're talking about
> evil programming, maybe it should be....

Probably but then again I don't think there needs to be much in a ant.* 
namespace ;) The one property that I think *should* be in namespace are 
ant.version (useful for future compatability).

The others (ant.home, ant.project.name, ant.file etc) are essentially 
work-arounds because ant currently doesn't have a great interface between 
tasks and the runtime (however hopefully this will change in Ant2). 

-- 
Cheers,

Pete

----------------------------------------------------------------
Fools ignore complexity.  Pragmatists suffer it.
Some can avoid it.  Geniuses remove it.
-- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982
----------------------------------------------------------------