There are many ways to organise build systems for Java projects. The two most predominant are probably still Ant and Maven. Debates between the two tend to go around in circles with the balance now swinging towards maven - since IDE support has got better (particularly Eclipse). My own view is if you do not have a good architecture which is modular in nature and which separates concerns that should be separated you'll run into trouble no matter what you use. The emphasis should always be on good architecture first and foremost.
That said, I made this short video which illustrates some of the arguments you hear from Maven-ites and Ant-ists. It is a debate between Maeve and Anthony. Maeve is arguing for Maven; Anthony is arguing for Ant. Obviously, it's impossible to cover every single argument but the video includes some of the principle ones. Get some popcorn and enjoy.
That said, I made this short video which illustrates some of the arguments you hear from Maven-ites and Ant-ists. It is a debate between Maeve and Anthony. Maeve is arguing for Maven; Anthony is arguing for Ant. Obviously, it's impossible to cover every single argument but the video includes some of the principle ones. Get some popcorn and enjoy.
Congrats! Very cool video! I wonder why there is no Gradle guy participating ??? :-)
ReplyDeleteBest regards,
Kai Wähner (Twitter: @KaiWaehner)
Good point Kai. Will do Gradle when I get some time :-)
ReplyDeleteVery nice.
ReplyDeleteGet the best of both worlds by using "maven ant tasks". This allows you to get all of the convenience of dependency management from a maven pom file along with the flexibility and power of ant.
http://maven.apache.org/ant-tasks/index.html
Great intro Alex. Useful for somebody who has used ANT for 6 1/2 years but not MAVEN : )
ReplyDeleteShort and nice video
ReplyDelete