ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <>
Subject Re: <ant> nesting - Issue #5662
Date Mon, 21 Jan 2002 08:05:14 GMT
On Mon, 21 Jan 2002 02:13, Erik Hatcher wrote:
> What do folks think should be done, if anything, about this particular
> issue?
> Nesting <ant> calls seems reasonable in componetized builds but having the
> first <ant> to set a property as a user property really ruins it for builds
> down the line because it can't be overridden using nested <property>.
> I'm particularly frustrated by the current behavior, but folks might be
> relying on the current functionality so changing it would affect them.
> Is this viewed as a bug?  If so then changing it would be reasonable.

It looks like a bug. I would have the following order of precedence if 

1. Properties set in ant task become "User properties"
2. "User Properties" of containing build file copied to new project as "User 
3. Regular Properties of containing build file copied to new project

Like that ?

> Are there workarounds to this?  Or perhaps a way to have the current
> functionality and had a switch such that properties being set from nesting
> under <ant> aren't set as user properties but rather regular properties?

It would break a bunch of my builds to make them regular properties ;) 



We should take care not to make the intellect our 
god; it has, of course, powerful muscles, but no 

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message