It seems to me that Maven is great for general things, but if something very specific needs to be done, Ant build files allow you to specify the nitty gritty details. If Maven can do absolutely everything that the Ant build can do, then My vote is to provide Maven functionality, but don't remove the Ant build so that people like me who haven't been completely swayed to make the switch to Maven can still build Log4j.
It can. In fact, you can specify "pre" and "post" targets so that your ANT specific code can be embedded before or after the internal Maven one does. It's great and it works well.
I have some experience with this issue since I wrote the build file for the Prevayler project ( http://www.prevayler.org/ ). There is a Maven project file, but my build file does things such as providing targets for running demos and building contrib projects that I don't see how Maven can provide since it is a general build tool that pretty much only allows you to do things the way that it wants to you to do things. It can't predict subtleties that one might want in a build. Am I wrong here? Am I just really missing something? Is Maven just so flexible that I should be able to do anything and everything that Ant allows for in an easier to configure and more organized way? I'd love to believe that.
Jake
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
