Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Message-ID: <2BBB61F98137D211A7C900805FB7568706F9D350@exlon04.lehman.com>
From: "Taylor, Jeremy" <jtaylor@lehman.com>
To: "'ant-user@jakarta.apache.org'" <ant-user@jakarta.apache.org>
Subject: RE: Dynamic binding of properties
Date: Thu, 5 Oct 2000 12:00:04 +0100 
MIME-Version: 1.0
Content-Type: text/plain

May I suggest 3 scopes; target, file and project? Where project is the
default scope and;

- target is valid only within the current target

- file is valid only within the current file ... i.e. not propogated to
called scripts 

- project is valid in the current project and all sub-projects

> -----Original Message-----
> From:	Michael Stanley [SMTP:mstanley@twcny.rr.com]
> Sent:	05 October 2000 09:20
> To:	ant-user@jakarta.apache.org
> Subject:	RE: Dynamic binding of properties
> 
> > > One thought is to associate a priority value with
> > > each property and only allow it to be changed at the same or higher
> > > priority. That introduces mutability with precedence.
> > Personally I think it
> > > is the way to go.
> 
> This is a good idea but is it the best idea?  Its apparent that Ant is
> slowly evolving into its own little programming language with global
> variables, methods, etc.  Maybe a better idea would be the introduction of
> target / project scope.  Final, static, instance vars, and even
> parameters.
> It just seems like this method (although more difficult) will lead itself
> to
> easier and more fluent evolution of Ant in the long run.
> 
> My 2 Cents,
> Mike