ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Alberto Fernandez" <>
Subject RE: [PATCH] Support for default ProjectHelper to expand properties in attributes to project/target tags
Date Mon, 05 Jan 2004 11:27:09 GMT
> From: Kenneth Olving [] 
> Hoping that I've managed to navigate all the etiquette for 
> posting a patch, here goes:
> Change made in brief:
> The default ProjectHelper ( has had two 
> lines changed so when parsing attributes for the 
> project/target tags, values will be passed through 
> Project.replacePropeties().
> Rationale:
> Given a build.xml like this:
>   <project default="${foo}">
>     <target name="bar">
>       <echo message="Hello world!"/>
>     </target>
>   </project>
> it allows for running this using something like this:
>   ant -Dfoo=bar
> and get the expected result. This type of usage isn't very 
> useful of course; my desire for this functionality comes from 
> that I'm using Ant embedded in my tool and that tool makes 
> sure there are appropriate properties set.

I feel unconfortable about this change. It introduces some sort of
dynamic programming with I do notknow which consequences. What happens
when people use <antcall/>?, what happens when depends lists contain
such variables? I think it is a very bad can or worms, unless we first
have a rational for it from ANT, the language, semantic point of view.

Kenneth, in your particular case, why can your particular tool just 
call "ant bar", I see no reason for limiting to use the default target.

Jose Alberto

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

View raw message