1.1 Maven Overview
MAVEN provides a comprehensive package of software project management. Whether it's compiling, publishing, documentation, or teamwork, MAVEN provides the necessary abstraction that encourages reuse and does a lot of work beyond software construction.
1.1.1 What is Maven
MAVEN is a set of project management frameworks, but this is not the whole of MAVEN. It is the most obvious definition of three words that Maven's author can get. But the name is a meaningless abstraction that doesn't express the power and complexity of maven. Too many technicians use three or four keywords To describe complex topics, and to reuse things like "project Management" and "enterprise software start" without expressing their specific meaning.
When someone wants to know what MAVEN is, they usually ask "what is maven?" and then they look forward to a short, outlined answer, "Well, it's a build tool, or a scripting framework." Maven can't use the boring, meaningless words to explain. It is a combination of ideas, standards, and software, and it is almost impossible to extract a definition for a simple, descriptive definition. The idea of innovation is often difficult to express clearly in words. If you're a comprehensive on maven, Rich definitions of interest, you can read this introduction. It will first want you to provide the concepts and theories you want to follow. If you read this introduction, just to find something to tell your supervisor, you can go to chapter two now.
If Maven is not a "project management framework", what is it? Here's a description: Maven is standard, storage format, and some software for managing and describing projects. It defines a standard lifecycle for building, testing, and deployment projects. It provides a framework that allows all projects that follow the MAVEN standard to facilitate the reuse of common build logic. The MAVEN project exists in the Apache Software Foundation, an Open-source community that develops software tools based on a common software object model (Project object models), or POM. This book focuses on the core part of the Maven project,--maven 2, a very good tool that greatly simplifies the management process of the software project.
You may have expected a more straightforward answer, and maybe you picked up the book because someone once told you that MAVEN is a building tool. Don't worry, Maven can do a build tool you're looking for, and many developers who use Maven as another build tool get a good tuning build system. When you plan to use MAVEN as "another build tool," Look at Maven in this limited way, just like saying that Web browsers are just looking at hypertext.
Maven and the technology associated with it have started to create a change in the Java community.
In addition to addressing issues that are simple to understand, and such as simplifying builds, documents, publishing, and deployment processes, Maven brings more and more compelling benefits.
More and more projects and products use MAVEN as the basis for their project management. It becomes easy to build relationships between projects and build systems, and to navigate and report on this relationship. The standard format for MAVEN allows you to use a "semantic Web" for project encodings. MAVEN's specification and central warehouse define a brand new naming system for the project. Using MAVEN, you can easily add other dependencies and publish your own components.
So, now to answer the original question: Maven has different uses for different people. It's a series of standards and solutions, not just software. It is a way of dealing with a series of software that is described as a set of interdependent components, using a uniform format. It is a way for individuals and groups to collaborate to develop software systems in the future. Once you understand Maven, you'll wonder how it was developed before.