ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John.D.Ca...@mail.sprint.com
Subject RE: Re: <exec> problem with exit value
Date Tue, 10 Apr 2001 14:16:31 GMT
+10000000 on that!

John

-----Original Message-----
From: glenn [mailto:glenn@somanetworks.com]
Sent: Tuesday, April 10, 2001 8:23 AM
To: ant-dev
Cc: glenn
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
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message