ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <>
Subject Re: Configure->Template->Build
Date Thu, 31 May 2001 10:50:48 GMT
At 11:53 AM 5/31/01 +0200, Stefan Bodewig wrote:
>Peter Donald <> wrote:
>> Nope - only those who need the power will use it. Most people can
>> live within bounds of current day ant.
>I'm not sure that this is true.  Every now and then there is somebody on
>ant-user who asks how he could compile more than one file.  Give them
>the documentation of javac (which is good in explaining what the task
>does IMHO) and document that describes how to invoke the same task
>over and over again while looping over a set of files - what are they
>going to chose?

I am not following you here ;) I would choose the first approach.

>>>> * the need for per task failonerror (better solved with templating
>>>> - which needs configure stage to run first).
>I thought that would become an aspect?

good point - bad example.

>>>> anton/javaon/etc are all ugly hacks to get dynamic templating
>>>> which should be done via Configure+templating (ie configure
>>>> generates list of classes/directories while templating applies
>>>> rule).
>How could this work if the files/directories in question are not there
>at configure time but created during the build time - or the build
>deletes other files?

Almost all of these can be statically generated from precursor products.
For instance in many makefiles you build static lists of .o files in an
output directory even though they are generated at runtime. I can not think
of a legitimate reason not to have static mapping - can you ?



| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |

View raw message