Ant.java + inhert proeprties flag

[Peter Donald <do...@apache.org>]

Hi,

first time I had to use Ant/CallTarget in moderately complex manner and I
realized that what a whole bunch of people were saying ages ago was right.
Overiding/not-Overiding things does suck ! So what do you thing of adding
an attribute "inheritproperties" for ant task which only inherits current
build files properties if set to true. Defaults to false for backwards
compatability ?


Cheers,

Pete

*------------------------------------------------------*
| "Computers are useless. They can only give you       |
|            answers." - Pablo Picasso                 |
*------------------------------------------------------*

Re: Ant.java + inhert proeprties flag

[Stefan Bodewig <bo...@apache.org>]

Peter Donald <do...@apache.org> wrote:

> first time I had to use Ant/CallTarget in moderately complex manner
> and I realized that what a whole bunch of people were saying ages
> ago was right.

welcome to the club 8-)

> So what do you thing of adding an attribute "inheritproperties" for
> ant task which only inherits current build files properties if set
> to true. Defaults to false for backwards compatability ?

Defaults to *true* for backwards compatability, isn't it?

Actually I don't think it would be a good idea to change that right
now, we know we are going to break whatever hack gets into 1.3 in Ant2
anyway. Adding a new feature in 1.3 implies that we are going to
support it in 2.x as well IMHO and this may very well not be true for
what you propose.

Given that -1 should mean "I will help to implement a better
solution", make that a -0 for now ;-). I don't know any other solution
ATM.

Stefan

RE: Ant.java + inhert proeprties flag

[Joshua Davis <js...@bellatlantic.net>]

> -----Original Message-----
> From: Nico Seessle [mailto:Nico.Seessle@epost.de]
> Sent: Tuesday, January 23, 2001 4:38 AM
> To: ant-dev@jakarta.apache.org
> Subject: Re: Ant.java + inhert proeprties flag
>
> > first time I had to use Ant/CallTarget in moderately complex manner and
I
> > realized that what a whole bunch of people were saying ages ago was
right.
> > Overiding/not-Overiding things does suck ! So what do you thing of
adding
> > an attribute "inheritproperties" for ant task which only inherits
current
> > build files properties if set to true. Defaults to false for backwards
> > compatability ?
>
> "false"? Doesn't it put all the properties in there by default? (at least
> for antcall it does).
>

In the 1.2 release, the properties of the parent override those of the child
in <ant> and <antcall>.  Haven't tried the latest stuff from CVS yet (I'm a
chicken). :)

+1 for me on this idea, although the committers are nearing a 1.3 release so
this may have missed the train.

I've been working on a little modification to <ant> that has a
'propertyfile' attribute so the user can specify a file to load the
properties from.

Re: Ant.java + inhert proeprties flag

[Nico Seessle <Ni...@epost.de>]

----- Original Message -----
From: "Peter Donald" <do...@apache.org>
To: <an...@jakarta.apache.org>
Sent: Tuesday, January 23, 2001 9:48 AM
Subject: Ant.java + inhert proeprties flag


> Hi,
>
> first time I had to use Ant/CallTarget in moderately complex manner and I
> realized that what a whole bunch of people were saying ages ago was right.
> Overiding/not-Overiding things does suck ! So what do you thing of adding
> an attribute "inheritproperties" for ant task which only inherits current
> build files properties if set to true. Defaults to false for backwards
> compatability ?

"false"? Doesn't it put all the properties in there by default? (at least
for antcall it does).

Nico