In all likelihood, people migrating to Maven have been using Ant. They've invested a lot of time in building Ant scripts and have found the major failings due to lack of simple reusability of scripts etc. That's why they're trying to use Maven. (You can read these last sentences as... I'm trying to convert from Ant to Maven. I didn't like the lack of simple reusability in Ant. I'm trying to use Maven).
I'd like to suggest a separate offshoot of the FAQ which would be a migration from Ant FAQ. With reams of information showing ways to convert parts of your build from ant to maven. Some of the things I can think of straight off the bat. * Terminology differences (build.xml vs. maven.xml / project.xml) * Why you'd want to use Maven over Ant. The front page goes on about "Project Comprehension" which is good and all, but the fact that maven can do in 0 lines what ant takes 50 lines to do for a simple project is a big selling point in my opinion (provided you use the default directory structure). * Why you'd want to use Ant over Maven. * Launching an ant script from Maven. For those things that just don't convert / don't make sense to convert. * Copying a file and replacing properties on the way through * Writing a dependant task (pregoalling I think it's called) / postgoalling Now I'll do a draft xdoc (and maintain it) for this (if there is interest), and I'll try and cull answers from the mailing list to cover off new things as they come up. I realise that the answers to these questions aren't necessarily Ant specific, but that can be taken care of by judicious hyperlinking . Any comments? Cheers, Ben -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
