I understand what you mean now. You want all possible values to be taken
care of. Not sure if I can think of anything off-hand that would do that.
On Tue, Mar 24, 2009 at 1:30 PM, Felix Dorner <fdor...@zed.com> wrote:
> Hey David,
>
> Thanks for your suggestions.
>
> > Well the only reason I specified the method below is that you
> > asked what could be done with ant-core.
>
> > However, if you're able to use ant-contrib, then you can
> > simplify it a little more using the ant-contrib <if> task.
>
> Of course this is a possibility, but it would assume I *know*
> all possible values that the property would ever take. (I know,
> I only spoke of a,b,c, but of course I'm trying to abstract as
> much as possible..
>
> And every time someone downstream wants to add a new possible
> property and a corresponding macro definition, he would
> need to write me an email and ask me to modify that piece
> of code to include his value.
>
> <macroExec name="${x}"/> would just pretty much nail it down.
>
> Felix
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
> For additional commands, e-mail: user-h...@ant.apache.org
>
>
--
"To be or not to be. That's not really a question." - Jean-Luc Godard
