Maksim Kabakou - Fotolia

Get started Bring yourself up to speed with our introductory content.

How to install Maven and build apps with the mvn command line

If you want to learn Maven and become a build master, the first step is to install Maven, and the second is to use the mvn command-line tool to compile and package Java apps.

Apache Maven forms the backbone of build tools like Gradle, continuous integration tools like Jenkins and even development tools like Eclipse. But because these aforementioned products often abstract Maven away, many developers have never had any reason to properly learn Maven fundamentals. This tutorial will help to quickly address that build tool knowledge shortcoming by demonstrating how easy it is to install Maven, create a Maven project and run a simple build job using the mvn command-line tool.

How to install Maven

A Maven install is one of the easier software installations you can do. At a high level, the steps to install Maven are:

  1. Download Maven binaries from the Apache website.
  2. Unzip the Apache Maven download, and move the folder to a place on your computer where you keep all of your other DevOps tools.
  3. Add system variables named MAVEN_HOME and M2_HOME, and point both of these variables to the root Maven directory. The root Maven directory will contain a folder named \bin, which contains the pivotally important mvn command-line utility.
  4. The root Maven directory contains a subfolder named \bin. Add this \bin directory to the OS' path. This makes the mvn command-line tool universally available to the OS.

In my personal development environments, I like to rename the Maven directory _maven, and when I install Maven on a Windows machine, I place that folder directly in the root of the C: drive. Here's how the system variables and edited path look after you successfully configure and install Maven.

How to set M2_HOME and MAVEN_HOME system variables.

Learn Maven with the mvn command line

If you want to learn Maven, you need to make sure your Maven install was successful, and you can't be completely sure of that until you have successfully invoked the mvn command-line tool. When you install Maven on Windows, check the mvn by entering the following command on the DOS prompt:

C:\>mvn --version

DOS prompt
Enter C:\>mvn --version.

Prerequisites to install Maven

If you look at the console output generated from the mvn command-line tool, you will notice both the Java version and Java home directories are listed. This is a Maven prerequisite, so before using Maven, first install a Java Development Kit (JDK) and configure the JAVA_HOME system variable. When Maven compiles and runs Java code, it uses the preinstalled JDK tools to do so. Maven doesn't have any facilities to compile Java code itself.

Create a Maven project

Maven has stringent expectations on how to structure a software project, so it's best to ask the mvn command-line utility to create a Java project, rather than to create one by hand. To do so, just create a folder in which you want your Maven project to reside, and then, issue the following command:

mvn -B archetype:generate

Note how the above instruction is broken over four lines due to formatting constraints, but when executed in a scripting environment, it should all be contained on a single line, lest you will receive a Failed to execute goal error.

This command instructs the tool to create a Maven project named install-maven-tutorials (the artifactId). This command also indicates that all Java code will be placed under a set of subfolders that map to the package name com.mcnz.maven (the groupId). The command itself might look a little bit intimidating, but quite frankly, this command is probably the most difficult task for people who want to learn how to install and use Maven. Furthermore, when you look at the structure of the Maven project this command creates, the switches and flags used in the mvn command will make much more sense.

Maven directory structure

Maven can create a variety of different projects, from a microservice to a Spring Boot application, depending upon what type of Maven archetype you specify. The command used in this Maven tutorial simply uses a default Maven archetype, which maps to a basic Java project.

In my personal development environment, I ran this Maven command from a folder named _maven projects. The command then created a new Maven project folder named install-maven-tutorial, based on the -DartifactId switch. Maven also created an impressive branch of folders under the project for separating test code from application source code. The default Maven directory structure looks as follows:



Along with the impressive directory structure, the Maven command also created three additional files:

  1. pom.xml

A Maven POM example

A key objective when you learn Maven is to understand the role of the pom.xml file. The POM (Project Object Model) file describes how to build a given project, how the code should be packaged when it is deployed and any dependencies upon which the project relies.

When you look at the pom.xml file that was generated when the Maven project was created, you will notice it contains the artifactId and groupId properties that were specified when you ran the mvn command-line utility. In addition, Maven has indicated through the version property that this is a snapshot version. You can use the packaging property to package and deploy the project as a JAR file. You can also see from the dependency management section that you will use the JUnit during the test lifecycle phase.

Here's the Maven POM example file generated when you execute the task to create a new Maven project.

  <!--Install and learn Maven tutorial-->



Sample Maven Java files

Along with the pom.xml file, Maven provides two Java classes named and to help get your project started. The file simply contains a basic Hello World application.

package com.mcnz.maven;

/* from the install Maven tutorial.*/

public class App {
    public static void main( String[] args ){
        System.out.println( "Hello World!" );

The file simply contains a simple JUnit test that will always pass.

package com.mcnz.maven;
import junit.framework.*;

/* from the install Maven tutorial.*/

public class AppTest extends TestCase{

    public void testApp(){
        assertTrue( true );


Run a Maven build job

These two Java files aren't particularly interesting, but they do allow you to test some key Maven build facilities, such as compiling code, running tests and packaging an application. Run the following command from the root folder of the project. It will compile the code in the file, run the JUnit test in the file and zip and package the compiled code in a JAR file.

C:\_maven projects\install-maven-tutorial>mvn compile test package

Compile java
Compile Java code using the mvn command.

Package apps with the mvn command

As the mvn command-line utility runs, Maven will display the results of compilation, communicate the results of any failed JUnit test and specify the location of the packaged application. In this instance, the mvn command has created a new folder in the project named target and added a file to that folder with the following name: install-maven-tutorial-1.0-SNAPSHOT.jar.

mvm command
The results of the mvn command-line tool compiling and packaging an application.

Use the mvn command line to learn Maven

And that's all there is to it if you need to know how to install Maven and are interested in performing a simple build using the mvn command-line utility. It's really not that hard to learn Maven. Of course, there wasn't a great deal of Java development in this exercise, but with the Maven directory structure created, the pom.xml file added to the root of the project and sample source code provided, that can be addressed when the developer begins to write code. The process will be much easier to do with Maven taking care of the testing, compiling and packaging.

TheServerSide Maven guide

Part 1 -- "How to install Maven and build apps with the mvn command line"

Part 2 -- "Fix broken builds with this log4j Maven dependency example"

This was last published in May 2018

Dig Deeper on Java Development Tools

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

Why have so many enterprise Java developers been reticent to learn Maven, and what's the best way to remedy that problem?
I think it's like driving a car: many people can drive a car (or they think they can... :-)) but they have absolutely no clue as to how the engine under the hood is working.  Do you need to know that to drive a car?  Not really, no...

Same for nowadays powerful IDE's like Android Studio (based on the extremely powerful IntelliJ): they take the deep-down boilerplate stuff out of your hands so that you can concentrate on the "important", core business part of the job.

Does that mean stuff like Maven and Gradle is not important?  Absolutely not, but those IDE's make it less worth to investigate lots of time in something you normally won't use later on.  And something that you don't maintain, you forget.  So, why taking it up in the first place then.

I don't think it's because of laziness of the programmer, for sure not, but it's a matter of efficiency.  My guess...

Until you hit the wall and you're out of your comfort zone (that is, the powerful IDE is not at your side any more) so you have no other option than digging into it.  And that's where articles like yours come into the spotlight.

You've motivated me to write an article about the myth of the 'lazy programmer.' I addressed it briefly in this article that pushed:

But I think it deserves a post on its own.
Hi Cameron,

When I follow your tutorial and want to run the final JAR file through the command java -jar install-maven-tutorial-1.0-SNAPSHOT.jar, I get the following error: no main manifest attribute, in install-maven-tutorial-1.0-SNAPSHOT.jar.

Am I missing something?

I found a way around, adding this piece of code to the end of the pom.xml file (just before the closing </project> tag):

        <!-- Build an executable JAR -->
That did the trick, but I have absolutely no idea (yet) as to why this isn't added by default by the Maven setup framework.

You can't just make up your own steps after my tutorial ends!

You are 100% correct. This build makes a JAR that is best packaged as a library that other programs could use, although the fact that the one method in the one class has a main method would certainly imply runnability.

I think I'll update this tutorial to indicate that and show how to run the jar by linking to the compiled class directly, and create a separate article on using Maven and Gradle to create an executable JAR.

The is actually a tutorial coming up on the Maven plugin for Tomcat that shows how to create an executable JAR with an embedded Tomcat server hosting a web application, although that goes far beyond the 'get' of just running a basic JAR.

Guess I better get writing.