Maven introduction

Maven introduction :-

Maven is a build management tool from the Apache Software Foundation. Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven. It is used for projects build, dependency and documentation.

Maven’s Objectives -

1. Making the build process easy
2. Providing a uniform build system
3. Providing quality project information
4. Providing guidelines for best practices development
5. Allowing transparent migration to new features

Maven life cycle

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

For example, the default lifecycle has the following build 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.



When the default lifecycle is used, Maven will first validate the project, then will try to compile the sources, run those against the tests, package the binaries (e.g. jar), run integration tests against that package, verify the package, install the verifed package to the local repository, then deploy the installed package in a specified environment.

If you call a build phase, it will execute not only that build phase, but also every build phase prior to the called build phase.

for example :-

mvn package will do every build phase before it (validate, compile, test), before executing package.

Maven Advantage -

1. Standardization
2. Dependency management : Maven download the JAR, and putting it in the right place is really convenient.
3. Build lifecycle management
4. Project Modularization

Related posts :-
Spring Mvc Hello World Example With Annotation
Spring mvc example with maven using eclipse