I agree. When you are respsonible for a product with very specific requirements as to what compiler, what libraries, etc are used, you do NOT want a build tool to be an eager beaver and just go run with anything it can find. There is this requirement for a defined, controlled, repeatable process...
-1000 for anything like this. Diane Holt wrote: > I agree about not losing the compiler property -- I need to specify which > compiler is being used going in. > > But I have to disagree with this idea: > > > And, I also think, that old modern and classic compilers should be > > special, I mean, if I set compiler to be jikes, and jikes is not > > installed > > on the user site, current ANT throws an exception. I think more robust > > would be to issue a warning, and try to compile with modern, and if this > > one is not present either, try classic. Thus it would be great in case > > of failure of any "custom" compiler, trying modern then classic. > > This would be a very bad idea, as far as I'm concerned -- I can't just > have things compiling willy-nilly with any old compiler Ant happens to > find. Yikes! Which compiler I'm using needs to be a very controlled aspect > of the build. > > Diane > > ===== > ([EMAIL PROTECTED]) > > __________________________________________________ > Do You Yahoo!? > Yahoo! Shopping - Thousands of Stores. Millions of Products. > http://shopping.yahoo.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
