ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <>
Subject Re: over-riding properties and the concept of scope
Date Fri, 06 Jul 2001 07:00:37 GMT
On Fri,  6 Jul 2001 16:25, Stefan Bodewig wrote:
> > Hopefully ant2 will have some *explicit* method for a lower level to
> > override the upper levels, one that can be grepped for so that the
> > build engineer can catch it if someone overrides something they
> > shouldn't in a lower level buildfile.
> I prefer a mechanism that allows the build engineer to specify which
> properties may be overridden and which must not.  Making it impossible
> to override "something they shouldn't" is even better than having to
> grep for inappropriate usage every now and then IMHO.

This concept seems to align with the notion of "public" properties (ie ones 
that can be accessed and set from another project). Effectively the "public" 
properties become the data interface through which things can be modified. 
(as compared to operation/target interface).

So we could have public properties (things that can be set outside the 
project), public targets (things that can be called from outside project) and 
coresponding private proeprty/targets which are controlled internally by 
build file.



| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |

View raw message