Setup Menus in Admin Panel

Apache Maven


1 what is maven?

1.1 Maven’s Origins.

1.2 Comparison of Maven with Apache ANT

1.3 Maven’s Principles.

1.4 Key features of Maven.

1.5 Maven’s project object model (POM).

1.6 Maven Build Life Cycles, Phases and Goals.

2 What is Maven and how do I install it?.

3. Maven Repository.

3.1 Maven Local Repository.

3.2 Maven Central Repository.

3.3 Maven Remote Repository.

4.How to Create a Maven Project.

4.1 Create a Maven Java Project using Command Prompt.

4.2 Create a web application project using maven.

4.3 Create an Enterprise Project using Maven.

4.4 Create a Maven Java Project in Eclipse.

4.5 Create Maven Web Project in Eclipse.

5 Maven Plugins.

5.1 Plugin Types.

5.2 How do I deploy a maven web application to Tomcat?

5.3 How to Create a .war file from Eclipse using Maven Plugin?

6.Scopes of Maven.

7 create a multi-module project in Eclipse.

1 what is maven?

Maven encompasses a set of build standards, an artifact repository model, and a software engine that manages and describes projects. It defines a standard life cycle for building, testing, and deploying project artifacts.

 “Maven is a declarative project management tool that decreases your overall time to market by effectively leveraging cross-project intelligence. It simultaneously reduces your duplication effort and leads to higher code quality.”

To summarize: Maven is many things to many people. It is a set of standards and an approach to project development. Maven is  a collection of highly-interdependent components, which can be described in a common format.

It is the next step in the evolution of how individuals and organizations collaborate to create software systems.

1.1 Maven’s Origins

Maven was borne of the practical desire to make several projects at the Apache Software Foundation(ASF) work in the same, predictable way. Prior to Maven, every project at the ASF had a different approach to compilation, distribution, and Web site generation. The ASF was effectively a series of isolated islands of innovation. While there were some common themes across the separate builds, each community was creating its own build systems and there was no reuse of build logic across projects. The build process for Tomcat was different than the build process for Struts, and the Turbine developers had a different site generation process than the Jakarta Commons developers.

This lack of a common approach to building software meant that every new project tended to copy and paste another project’s build system. Ultimately, this copy and paste approach to build reuse reached a critical tipping point at which the amount of work required to maintain the collection of build systems was distracting from the central task of developing high-quality software.

Once developers spent time learning how one project was built, they did not have to go through the process again when they moved on to the next project. Developers at the ASF stopped figuring out creative ways to compile, test, and package software, and instead, started focusing on component development. The same standards extended to testing, generating documentation, generating metrics and reports, and deploying.

Like Maven Apache Ant is also a software tool for automating software build processes. It originally came from the Apache Tomcat project in early 2000.

History of Apache Ant

  • Ant was created by James Duncan Davidson (the original author of Tomcat).
  • It was originally used to build Tomcat, and was bundled as a part of Tomcat distribution.
  • Ant was born out of the problems and complexities associated with the Apache Make tool.
  • Ant was promoted as an independent project in Apache in the year 2000. The latest version of Apache Ant as on May 2014 is 1.9.4.

Features of ANT

  • Ant is the most complete Java build and deployment tool available.
  • Ant is platform neutral and can handle platform specific properties such as file separators.
  • Ant can be used to perform platform specific tasks such as modifying the modified time of a file using ‘touch’ command.
  • Ant scripts are written using plain XML. If you are already familiar with XML, you can learn Ant pretty quickly.
  • Ant is good at automating complicated repetitive tasks.
  • Ant comes with a big list of predefined tasks.
  • Ant provides an interface to develop custom tasks.
  • Ant can be easily invoked from the command line and it can integrate with free and commercial IDEs.

Hence Ant provides a toolbox for scripting builds, Maven provides standards and a set of patterns in order to facilitate project management through reusable, common build strategies.

1.2 Comparison of Maven with Apache ANT:

Major differences between Maven and ANT are:

  1. Maven is description of a project whereas ANT is development of a build script per project.
  2. Maven follows conventions like a common project directory structure whereas ANT needs to be told about the exactly where to find the source and where to put the output.
  3. Maven has invocation of defined goals (targets) whereas in ANT script you have invocation of project specific targets.
  4. Maven has build life cycle, standard project layout where as ANT doesn’t and it has too complex scripts(You have to define goals and goal dependencies). You have to attach a sequence of tasks to each goal manually.
  5. Maven has reusable plugins, repositories whereas ANT scripts are not reusable.
  6. Maven is declarative. All you have to do is create a pom.xml file and put your source in the default directory. Maven takes care of the rest.ANT is procedural which means you need to tell it to compile, copy and then compress.


1.3 Maven’s Principles

  • Convention over configuration
  • Declarative execution
  • Reuse of build logic
  • Coherent organization of dependencies

Convention over configuration

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 detail. When a Maven project is created, Maven creates default project structure. Developer is only required to place files accordingly and he/she need not to define any configuration in pom.xml.

Declarative execution

Everything in Maven is driven in a declarative fashion using Maven’s Project Object Model (POM) and specifically, the plugin configurations contained in the POM. The execution of Maven’s plugins is coordinated by Maven’s build life cycle in a declarative fashion with instructions from Maven’s POM.

Reuse of build logic

Maven promotes reuse by encouraging a separation of concerns (SoC). Maven puts this SoC principle into practice by encapsulating build logic into coherent modules called plugins.
In Maven there is a plugin for compiling source code, a plugin for running tests, a plugin for creating JARs, a plugin for creating Javadocs, and many other functions .  Plugins are the key building blocks for everything in Maven.

Coherent organization of dependencies

In Java, the most common artifact is a JAR file, but a Java artifact could also be a WAR, SAR, or EAR file. A dependency is a reference to a specific artifact that resides in a repository. A dependency is uniquely identified by the following identifiers: groupId, artifactId and version.

When a dependency is declared within the context of your project, Maven tries to satisfy that dependency by looking in all of the remote repositories to which it has access, in order to find the artifacts that most closely match the dependency request. If a matching artifct is located, Maven transports it from that remote repository to your local repository for project use.

1.4 Key features of Maven

  • Simple Maven project that follow Best practices required for Real time project.
  • Automate the build process – Compile, Package JAR/WAR, Deploy war in Server, Generate Report
  • Transitive dependencies (Inter dependency ex: To include commons-lang jar, it may again dependent on log4j jar, maven will automatically download the jar and include)
  • Dependency management: Maven encourages the use of a central repository of JARs and other dependencies
  • Extensible, with the ability to easily write plugins. Many plugins are developed to support compiling source code, deploying the war from work space to server, generate the report, generating stubs for web-service.
  • Build profiling – This feature will helps when we want to deploy the same code base in different environment such as DEV, QA , STAGE  , PRE-PROD, PROD  and we need to modify the Data Base URL, Third party URLS which are environmental dependent.
  • Maven supports multi-module project for re-usability of Module for different Project.Example: Common Façade & Service for Multiple Web Application, Common POM holding the Jar for Multiple Project to avoid duplication of jar etc.


1.5 Maven’s project object model (POM)

Maven is project-centric by design, and the POM is Maven’s description of a single project. Without the POM, Maven is useless – the POM is Maven’s currency. It is the POM that drives execution in maven and this approach can be described as model-driven or declarative execution.

The POM contains every important piece of information about your project. POM contains.

  • project – This is the top-level element in all Maven pom.xml files.
  • modelVersion – This required element indicates the version of the object model that the POM is using. The version of the model itself changes very infrequently, but it is mandatory in order to ensure stability when Maven introduces new features or other model changes.
  • groupId – This element indicates the unique identifier of the organization or group that created the project. The groupId is one of the key identifiers of a project and is typically based on the fully qualified domain name of your organization. For example org.apache.maven.plugins is the designated groupId for all Maven plugins.
  • artifactId – This element indicates the unique base name of the primary artifact being generated by this project. A typical artifact produced by Maven would have the form < artifactId >- <version> . <extension> (for example, myapp-1.0.jar ). Additional artifacts such as source bundles also use the artifactId as part of their file name.
  • packaging – This element indicates the package type to be used by this artifact (JAR,WAR, EAR, etc.). This not only means that the artifact produced is a JAR, WAR, or EAR, but also indicates a specific life cycle to use as part of the build process. The life cycle is a topic dealt with later in this chapter. For now, just keep in mind that the selected packaging of a project plays a part in customizing the build life cycle. The default value for the packaging element is jar so you do not have to specify this in most cases.
  • version – This element indicates the version of the artifact generated by the project. Maven goes a long way to help you with version management and you will often see the SNAPSHOT designator in a version, which indicates that a project is in a state of development.
  • name – This element indicates the display name used for the project. This is often used in Maven’s generated documentation, and during the build process for your project, or other projects that use it as a dependency.
  • url – This element indicates where the project’s site can be found.
  • description – This element provides a basic description of your project.

For a complete reference of the elements available for use in the POM please refer to the POM reference at


1.6 Maven Build Life Cycles, Phases and Goals

Maven has following three standard lifecycles:

  • clean
  • default(or build)
  • site

A Maven plugin is a collection of one or more goals. A goal is a “unit of work” in Maven.

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.

The order of execution depends on the order in which the goal(s) and the build phase(s) are invoked. For example, consider the command below. The clean and package arguments are build phases while the dependency:copy-dependencies is a goal.

mvn clean dependency:copy-dependencies package

Here the clean phase will be executed first, and then the dependency:copy-dependencies goal will be executed, and finally package phase will be executed.

Maven builds life cycle phases.

The following lists all build phases of the default, clean and site lifecycle, which are executed in the order given up to the point of the one specified.

Clean Lifecycle

executes processes needed prior to the actual project cleaning
remove all files generated by the previous build
executes processes needed to finalize the project cleaning


Default Lifecycle

validate the project is correct and all necessary information is available.
initialize build state, e.g. set properties or create directories.
generate any source code for inclusion in compilation.
process the source code, for example to filter any values.
generate resources for inclusion in the package.
copy and process the resources into the destination directory, ready for packaging.
compile the source code of the project.
post-process the generated files from compilation, for example to do bytecode enhancement on Java classes.
generate any test source code for inclusion in compilation.
process the test source code, for example to filter any values.
create resources for testing.
copy and process the resources into the test destination directory.
compile the test source code into the test destination directory
post-process the generated files from test compilation, for example to do bytecode enhancement on Java classes. For Maven 2.0.5 and above.
run tests using a suitable unit testing framework. These tests should not require the code be packaged or deployed.
perform any operations necessary to prepare a package before the actual packaging. This often results in an unpacked, processed version of the package. (Maven 2.1 and above)
take the compiled code and package it in its distributable format, such as a JAR.
perform actions required before integration tests are executed. This may involve things such as setting up the required environment.
process and deploy the package if necessary into an environment where integration tests can be run.
perform actions required after integration tests have been executed. This may including cleaning up the environment.
run any checks to verify the package is valid and meets quality criteria.
install the package into the local repository, for use as a dependency in other projects locally.
done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.


Site Lifecycle

executes processes needed prior to the actual project site generation
generates the project's site documentation
executes processes needed to finalize the site generation, and to prepare for site deployment
deploys the generated site documentation to the specified web server




December 31, 2015

0 responses on "Apache Maven"

Leave a Message

Your email address will not be published. Required fields are marked *

About Us

Pradeep Academy is an online & Training institute To make learning easy, interesting, affordable and accessible to millions of learners across the Globe. To create an alternative learning platform, using a unique learning methodology of live online interactive courses along with 24x7 support. We aim to empower our customers with skills which will help them get an edge in their careers and improve their lives.

Contact Us

Address :

PradeepIT Consulting Services Pvt Ltd

205,Brigade gardens, No.19 Church Street , Bangalore – 560001, Karnataka, India

Email :
Ph No: 08047363377
© Pradeep Academy.  Design & Developed by