通常部署过程包括以下步骤：

• 签入进入SVN或源代码存储库的所有项目的代码，并对其进行标记。

• 从SVN下载完整的源代码。

• 创建应用程序。

• Store the build output either WAR or EAR file to a common network location.

• Get the file from network and deploy the file to the production site.

• Updated the documentation with date and updated version number of the application.

Maven is a project management and comprehension tool. Maven provides developers a complete build lifecycle framework. Development team can automate the project"s build infrastructure in almost no time as Maven uses a standard directory layout and a default build lifecycle.

Maven uses Convention over Configuration which means developers are not required to create build process themselves. Developers do not have to mention each and every configuration details.

Maven provides developers ways to manage following −

• Builds

• Documentation

• Reporting

• Dependencies

• SCMs

• Releases

• Distribution

• mailing list

Type the following command −

mvn --version

POM stands for Project Object Model. It is fundamental Unit of Work in Maven. It is an XML file. It always resides in the base directory of the project as pom.xml. It contains information about the project and various configuration details used by Maven to build the project(s).

POM contains the some of the following configuration information −

• project dependencies

• plugins

• goals

• build profiles

• project version

• developers

• mailing list

An artifact is a file, usually a JAR that gets deployed to a Maven repository. A Maven build produces one or more artifacts, such as a compiled JAR and a "sources" JAR.

Each artifact has a group ID (usually a reversed domain name, like com.example.foo), an artifact ID (just a name), and a version string. The three together uniquely identify the artifact. A project"s dependencies are specified as artifacts.

A Build Lifecycle is a well defined sequence of phases which define the order in which the goals are to be executed. Here phase represents a stage in life cycle.

The three build lifecycles are −

• clean:cleans up artifacts created by prior builds.

• default (or build):This is used to build the application.

• site: generates site documentation for the project.

Type the command −

mvn site

This command removes the target directory with all the build data before starting the build process.

Following are the phases −

• validate − validate the project is correct and all necessary information is available.

• compile − compile the source code of the project.

• test − test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed

• package − take the compiled code and package it in its distributable format, such as a JAR.

• integration-test − process and deploy the package if necessary into an environment where integration tests can be run.

• verify − run any checks to verify the package is valid and meets quality criteria.

• install − install the package into the local repository, for use as a dependency in other projects locally.

• deploy − done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.

A goal represents a specific task which contributes to the building and managing of a project. It may be bound to zero or more build phases. A goal not bound to any build phase could be executed outside of the build lifecycle by direct invocation.

This command will clean the project, copy the dependencies and package the project (executing all phases up to package).

The clean lifecycle consists of the following phases −

• pre-clean

• clean

• post-clean

The phases in Site Lifecycle are −

• pre-site

• site

• post-site

• site-deploy

A Build profile is a set of configuration values which can be used to set or override default values of Maven build. Using a build profile, you can customize build for different environments such as Production v/s Development environments.

Build profiles are of three types −

• Per Project − Defined in the project POM file, pom.xml.

• Per User − Defined in Maven settings xml file (%USER_HOME%/.m2/settings.xml).

• Global − Defined in Maven global settings xml file (%M2_HOME%/conf/settings.xml)

A Maven Build Profile can be activated in various ways −

• Explicitly using command console input.

• Through maven settings.

• Based on environment variables (User/System variables).

• OS Settings (for example, Windows family).

• Present/missing files.

A repository is a place i.e. directory where all the project jars, library jar, plugins or any other project specific artifacts are stored and can be used by Maven easily.

Maven repository are of three types: local, central, remote

Maven local repository is a folder location on your machine. It gets created when you run any maven command for the first time. Maven local repository keeps your project"s all dependencies (library jars, plugin jars etc).

~/m2./repository.

mvn install

It is repository provided by Maven community. It contains a large number of commonly used libraries. When Maven does not find any dependency in local repository, it starts searching in central repository using following URL: http://repo1.maven.org/maven2/.

Sometimes, Maven does not find a mentioned dependency in central repository as well then it stops the build process and output error message to console. To prevent such situation, Maven provides concept of Remote Repository which is developer"s own custom repository containing required libraries or other project jars.

Following is the search pattern −

• Step 1 − Search dependency in local repository, if not found, move to step 2 else if found then do the further processing.

• Step 2 − Search dependency in central repository, if not found and remote repository/repositories is/are mentioned then move to step 4 else if found, then it is downloaded to local repository for future reference.

• Step 3 − If a remote repository has not been mentioned, Maven simply stops the processing and throws error (Unable to find dependency).

• Step 4 − Search dependency in remote repository or repositories, if found then it is downloaded to local repository for future reference otherwise Maven as expected stop processing and throws error (Unable to find dependency).

Maven Plugins are used to −

• create jar file.

• create war file.

• compile code files.

• unit testing of code

• create project documentation.

• create project reports.

Maven provides following two types of Plugins −

• Build plugins − They execute during the build and should be configured in the <build/> element of pom.xml

• Reporting plugins − They execute during the site generation and they should be configured in the <reporting/> element of the pom.xml

Maven dependency management using concept of Maven Repositories (Local, Central, Remote). Suppose dependency is not available in any of remote repositories and central repository; in such scenarios Maven uses concept of External Dependency.

External dependencies (library jar location) can be configured in pom.xml in same way as other dependencies.

• Specify groupId same as name of the library.

• Specify artifactId same as name of the library.

• Specify scope as system.

• Specify system path relative to project location.

Archetype is a Maven plugin whose task is to create a project structure as per its template.

Type the following command −

mvn archetype:generate

SNAPSHOT is a special version that indicates a current development copy. Unlike regular versions, Maven checks for a new SNAPSHOT version in a remote repository for every build.

In case of Version, if Maven once downloaded the mentioned version say data-service:1.0, it will never try to download a newer 1.0 available in repository. To download the updated code, data-service version is be upgraded to 1.1.

In case of SNAPSHOT, Maven will automatically fetch the latest SNAPSHOT (data-service:1.0-SNAPSHOT) everytime app-ui team build their project.

Transitive dependency means to avoid needing to discover and specify the libraries that your own dependencies require, and including them automatically.

It means to directly specify the versions of artifacts to be used when they are encountered in transitive dependencies. For an example project C can include B as a dependency in its dependencyManagement section and directly control which version of B is to be used when it is ever referenced.

Maven determines what version of a dependency is to be used when multiple versions of an artifact are encountered. If two dependency versions are at the same depth in the dependency tree, the first declared dependency will be used. This is called dependency mediation.

Dependency scope includes dependencies as per the current stage of the build. Various Dependency Scopes are −

• compile − This scope indicates that dependency is available in classpath of project. It is default scope.

• provided − This scope indicates that dependency is to be provided by JDK or web-Server/Container at runtime.

• runtime − This scope indicates that dependency is not required for compilation, but is required during execution.

• test − This scope indicates that the dependency is only available for the test compilation and execution phases.

• system − This scope indicates that you have to provide the system path.

• import − This scope is only used when dependency is of type pom. This scope indicates that the specified POM should be replaced with the dependencies in that POM"s <dependencyManagement> section.

{groupId,artifactId,type,classifier}.

To reference a property defined in your pom.xml, the property name uses the names of the XML elements that define the value, with "pom" being allowed as an alias for the project (root) element.

So ${pom.name} refers to the name of the project, ${pom.version} refers to the version of the project, ${pom.build.finalName} refers to the final name of the file created when the built project is packaged, etc.

Some of the valid packaging values are jar, war, ear and pom. If no packaging value has been specified, it will default to jar.

pom

The <execution> element contains information"s required for the execution of a plugin.

<groupId>:<artifactId>:<version>

All POMs inherit from a parent (despite explicitly defined or not). This base POM is known as the Super POM, and contains values inherited by default.

Profiles are specified using a subset of the elements available in the POM itself.

<repositories>, <pluginRepositories>,<dependencies>, <plugins> ,<properties>, <modules><reporting>,<dependencyManagement>,<distributionManagement>

To give portability to projects ( e.g. windows, linux etc).

It uses less storage, it makes checking out project quicker, non need for versioning JAR files.

Use the command −

mvn o package.

Using the exclusion element.

Dependency with scope system are always available and are not looked up in repository, they are usually used to tell Maven about dependencies which are provided by the JDK or the VM. Thus, system dependencies are especially useful for resolving dependencies on artifacts which are now provided by the JDK.

Any transitive dependency can be marked as optional using "optional" element. As example, A depends upon B and B depends upon C. Now B marked C as optional. Then A will not use C.

Any transitive dependency can be exclude using "exclusion" element. As example, A depends upon B and B depends upon C then A can mark C as excluded.

You can put the clean plugin inside the execution tag in pom.xml file.

set <inherited> to false.

It means that you have executed a plugin multiple times with the same <id>. Provide each <execution> with a unique <id> then it would be ok.

A mojo is a Maven plain Old Java Object. Each mojo is an executable goal in Maven, and a plugin is a distribution of one or more related mojos.

Ant is simply a toolbox whereas Maven is about the application of patterns in order to achieve an infrastructure which displays the characteristics of visibility, reusability, maintainability, and comprehensibility. It is wrong to consider Maven as a build tool and just a replacement for Ant.