Paul Hammant wrote: > We have a built in Ant. I have come to the conclusion that it does > not help us re acceptance. Newbies fear the scope of what we might > have done to Ant and why we would want to.
What is the fear? I think that it makes it a lot easier for newbies to get up and running with Avalon because they do not need to know Ant to be able to make use of Avalon. If we purged it, they would have to download, install and setup Ant before they could start working with Avalon. It is nice for projects to have their own copy of ant built into them so that they are self contained. As things are, users can just download the project and run the build script without having to understand what is actually doing the build. It is still possible for people to have another copy of Ant on their systems and make use of that for their own projects. Any of the "feared" changes that may or may not have been made to the copy of Ant which is used to build Avalon should not affect them. I believe that all we have done though was to add some additional jars. I may be missing something :-) but for now, I am -1 on purging ant from the build. Cheers, Leif -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>