Stefano Bagnara wrote: > When we agreed to remove ant it was obvious the build scripts > should be removed, too.
> Noel 22/5: "And I think it is time to upgrade our Ant to 1.6.5; > or perhaps remove Ant from our repository, and ask developers > to install it first." Yes ... "upgrade Ant or *perhaps* remove Ant from the repository." And when. There is the issue of timing. When would it be mutually convenient for people to adjust their systems to account for such a change? We have not only you, me, Bernd, Norman. We have other people on the list who build the code. And untold more who are not constantly active on the list. > I think that any developer using Java should know how to use ant, or > otherwise it should be better to not let him build James. Many projects provide instructions for building, e.g., http://svn.apache.org/viewvc/tomcat/build/tc5.5.x/BUILDING.txt. Interestingly, those that don't tend to have fewer people contributing. And when they add them, they have more. Our instructions are trivial, and should be expanded. > We can't take weeks and dozen of messages for each single commit. Depends upon the commit. Changing the build structure is not a big deal. It wasn't a high priority, either, but not a big deal. And it might open the way to using newer Ant features, which could help with multi-project issues, so that's a benefit. The risk involved was quite low. All that it cost was confusion, and temporarily broke the automated builds. Again, a simple e-mail along the lines of "Next Friday, a week from now, we will be ___. In order to prepare for ___, you will need to do ___.", and adding instructions to SVN, as I did, would have helped. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
