(Maven comes from Yiddish, meaning the accumulation of knowledge. It was first used in the Jakarta Turbine project to try to simplify the construction process. At that time, there were many projects whose Ant build files were only thin, while JAR files were protected by CVS. So Maven founders started the Maven project. The clear definition of this project includes a convenient method to publish project information and a method to share JARs in multiple projects. Maven is a project management tool, which includes a project object model, a set of specifications, a project lifecycle, a dependency management system, and the logic used to run the plug-in scheme (goal) defined during the life cycle. When you use Maven, you use a well-defined project solution model to describe your project. Then Maven can use crosscutting logic, which comes from a group of shared (perhaps customized) plug-ins. Maven has a life cycle, which is called when you run mvninstall. This command tells Maven to perform a series of orderly processes until you reach the specified life cycle. One of the impacts of traversing the life cycle is that Maven runs a lot of tacit plug-in solutions that enable office work such as compiling and creating a JAR file. In addition, Maven can easily help you manage project reports, generate sites, manage JAR files, and so on.
Maven Authoritative Guide Chinese Version. pdf)