ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hessu X <>
Subject Re: Deed need for preprocessing
Date Fri, 25 Aug 2006 17:01:31 GMT


I have considered splitting build file, but problem seems to be that process for different
"products" are partially same, partially not. And the situation is the same with actions and

Have to really think that, thanks.

Antoine Levy-Lambert <> wrote: Hello,

before you go the generation route, should you not first try to create a common build file
which your different build files would import and which would contain some common targets
and some macro definitions ?

If you absolutely have to do generation, XSLT is a possibility. I have also seen velocity
used to generate ant build files, it works and is kind of neat. I do not know webmacro nor


-------- Original-Nachricht --------
Datum: Fri, 25 Aug 2006 06:18:47 -0700 (PDT)
Von: Hessu X 
Betreff: Deed need for preprocessing

> Hello,
>   I am using ant to keep my projects in sensible order. It also gives me
> possibility efficient run of process by parallel tasks.
>   I am not building, just massaging builds to amount of different
> packages.
>   And I am not doing java.
>   I am looking something to shrink dozens of my partly hardcoded ant xml
> files for reasonable manner. I 'm very close to get in the situation of
> maintenance chaos (same data in several places etc). 
>   I thought something like preprocessor: it should take a project file and
> generate ant build file so I could feed it to ant with generated
> properties.
>   I have several options on checking :
>   * webmacro-2.0
>   * velocity
>   * xmlpreprocess
>   Any comments on these?!
>   More ideas?
> ---------------------------------
> Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small
> Business.

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

Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business.
  • Unnamed multipart/alternative (inline, 8-Bit, 0 bytes)
View raw message