ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Gregorovic" <den...@arsdigita.com>
Subject RE: <exec> problem with exit value
Date Tue, 10 Apr 2001 13:50:42 GMT
I recently faced the same issue which I solved by "fully qualifying"
each property that needed to be local.  So, 'src.dir' became
'componentA.componentB.src.dir', etc.  

-- Dennis

-----Original Message-----
From: glenn@dryline-fw.wireless-sys.com
[mailto:glenn@dryline-fw.wireless-sys.com]On Behalf Of Glenn McAllister
Sent: Tuesday, April 10, 2001 9:23 AM
To: ant-dev@jakarta.apache.org
Subject: Re: <exec> problem with exit value


Jose Alberto Fernandez wrote:

> This issue, just brings back to the front one of my old misgivings about the
> way <ant> works. The idea that all the properties from the calling project
> are inherited and inmutable in the called project seem to be wrong.
>
> I have no problem on having the caller's properties be as default values in
> the callee, but the callee should be able to set the values to locally. The
> only exception to these being values passed in the <property> arguments,
> which clearly should take presedence.
>
> Without these behavior, one would be force to know about all the properties
> of all the subprojects in my big project in order to not reuse some property
> name already used LOCALLY in some subproject.
>

This is not a small concern.  On one project I had *hundreds* of <ant> calls
with nested property elements, repeatedly calling about a dozen subprojects.
I had to be aware of all the properties I was using in the subprojects to not
use them in the "master" project.

Glenn



Mime
View raw message