1, Ant is programmed. You must tell Ant exactly what to do and when to do it. You have to tell it to compile, then copy and then compress.
2.Ant has no life cycle, and you must define the dependencies between goals. You must manually attach a task sequence to each target.
Apache Maven
1, Maven has a contract, because you follow the contract, it already knows where your source code is. It puts bytecode in target/classes, and then generates a JAR file at target.
2.Maven is declarative. All you need to do is create a pom.xml file and put the source code in the default directory. Maven will help you in other ways.
3.Maven has a life cycle, which will be called when running mvn install. This command tells Maven to perform a series of orderly steps until the specified life cycle is reached. One effect of the life cycle tour is that Maven runs many default plug-in targets that accomplish things such as compiling and creating JAR files.
Maven provides built-in intelligence for some common project tasks in the form of plug-ins. If you want to write and run unit tests, all you need to do is write the tests in/usr/local/Hudson/Hudson-home/jobs/maven-guide-zh-to-production/workspace/content-zh/src/test/Java, add a test range dependency for TestNG or JUnit, and then run mvn test.
If you want to deploy a web application instead of a JAR, all you need to do is change your project type to war, and then set your document root directory to/usr/local/Hudson/Hudson-home/jobs/maven-guide-zh-to-production/workspace/content-zh/src/main/webapp. Of course, you can do these things with Ant, but you need to write these instructions from scratch. To use Ant, you first need to determine where the JUnit JAR file should be placed, then you need to create a classpath containing this JUnit JAR file, then tell Ant where to find the test source code, write a target to compile the test source code into bytecode, and use JUnit to perform unit tests. Without the support of technologies such as Antlibs and lvy (even with these supporting technologies), ant gives people the feeling that it is a customized programmatic construction.
A group of efficient mavenpoms in the project abide by the contract and have only a little XML compared with Ant's configuration file.
Another advantage of Maven is that it relies on the widely used Maven plug-ins. Everyone uses the Maven Surefire plug-in to run unit tests. If someone adds some support to the new test framework, you can get new functions by upgrading the version of specific plug-ins in the project POM.
The decision to use Maven or Ant is not either-or, and Ant still has its place in complex structures. If your current build contains some highly customized processes, or you have written some Ant scripts to complete a certain process in a certain way, which is not suitable for the Maven standard, you can still use these scripts in Maven. As the core plug-in of Maven, Ant still exists. Custom plug-ins can be implemented with Ant, and Maven projects can be configured to run Ant scripts in the life cycle.