Recently study Maven, found that there are very few articles in this area. I have touched myself a few days, I saw a few articles, I feel that there is nothing comparable because it is functional that Maven is greater than Ant. But in fact, it is necessary to continue to integrate to choose Maven or AT, but also to see the specific needs, if you already have CruiseControl Ant, there is no need to be united CruiseControl maven, if you are now preparing to do continuous integration, then you Let's try Maven.
In fact, many times are more than the two things, because many times often use something to be more than their own personal preferences. For example, some people like to use jbuilder who like to use Eclipse, who is it? Who is it? I do not know. For Maven, we already have CruiseControl Ant, but I still want to turn into CruiseControl Maven, because I like Maven (my site I am doing the master). Saying a pile of no, I don't know the cloud, now I return to the topic to tell my comparison:
1: Function: Ant is used to build Java projects; while Maven not only contains build, but also manages Java projects
2: Build: Ant is to put the JARS required to build into classpath; Maven maintains a local repository responsible for storing JARS, such different projects can share a jars repository
3: Object: Maven references some concepts of some face objects (package and inheritance)
Last continued
