On Fri, 25 Jan 2002, Remy Maucherat wrote: > > Maybe I'm crazy, but so far I did a lot of the build.xml changes every > > time a new ant was released, with all the pain of trying (without > > 1.5 deprecates more attrbutes, BTW (don't know if you tried building Tomcat > with it).
I'll try. The attribute deprecation between 1.3 and 1.4 was IMHO completey unjustified, and if 1.5 does the same we'll have the same problem once again. > If we don't like Ant 2, why would we have to use it ? If it introduces big > changes in build.xml, why upgrade when Ant 1 works fine ? Sooner or later ant2 will be released and people will start using it in some projects - we can stick with ant1.4 if we want, but other projects will use ant1.5, some may stick with ant1.3 - it'll be a nightmare to build any collection of projects. And gump can't do too much - if you make build.xml work with ant2 it'll no longer work with ant1.4, same for the reverse. The problem is that the differences between 1.3 - 1.4 - 1.5 that caused us a lot of trouble are nothing compared with what seems to be happening in ant2. It would be much better getting ant2 to be (reasonably) backward compatible in the DTD than sticking with ant1.4. Costin P.S. I can volunteer to write the Makefiles, since soon this may be the cleanest way to build tomcat... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
