Hi,

I been thinking that to actually accomplish the flexability in the build
process that everyone seems to want we are going to either end up with a
forest of mangled scripts. For a while now I have been using another set of
bootstrap scripts that bootstrap the bootstrap ;) so as to enable all the
things that I want/don't want and to actually make it compile (ie define
CLASSPATH, define ANT_HOME, define JAVA_HOME, define JAVAC, define ... etc)

Ages ago bootstrapping current ant with an old ant was vetoed IIRC but I
would like to make a case for it. I would like to see an old version of ant
kept in CVS (say last released version). This would give us all heaps of
flexability and it would void the need for maintaining the complex
platforms specific scripts that we currently use. The main reason this was
vetoed last time was because it involved keeping jars in CVS and as this is
no longer  so taboo maybe we could change it ?

The only real other option is to build a Bootstrap.java that we use to
bootstrap the process. However this would be just as brittle and
unmaintainable as the other techniques - just in java. 

thoughts?


Cheers,

Pete

*-----------------------------------------------------*
| "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               |
*-----------------------------------------------------*

Reply via email to