[[ moved to general ]] Costin Manolache 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 > success ) to make it work with the old version and the new one. I suppose > Remy and Craig know what I'm talking about. Given that we use ant for > testing, and we already have a lot of ant files - please at least follow > the discussions, it'll affect us as well. I don't have the time or energy > to try to convince Peter and the others pushing for those changes...
You have to ask yourself: if Peter and others go off into left field, how many people will follow? The way I plan to participate in this discussion is through Gump. If Peter or Conor ever get to the point where they would like to propose a code base for Ant2, I'll start executing and posting trial runs against all of the projects that I follow. If there are small changes that people can make to their existing build scripts that will make them work equally well with Ant 1 and Ant 2, I will advocate that such changes be made. If not, then I will advocate that people avoid considering the new version just yet. I've done this before, and I am doing it for a number of activities: I nudged a number of projects along to Xalan2. This is largely done. The only remaining item is for Taglibs to either make the build of the Xalan1 conditional, or to drop it all together. I have nudged a number of projects along to Xerces 2. The remaining holdout has been Turbine. Once Xerces 2 releases, I plan to convert gump over wholesale and this should get some attention. I've been monitoring JDK 1.4. At this time, I honestly think the changes are too dramatic to push projects in that direction. The Ant2 activities are not even as far along as JDK 1.4. - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
