---

Installing Maven

Maven turns your human-readable Java code into executables that computers can run (a process called “building”). If you built your code manually (e.g. using a Unix/Linux makefile), you’d have to keep track of hundreds or thousands of steps and dependencies that might not be obvious. Maven takes care of all those complications in the background so you don’t have to.

---

Windows 10 with EclipseIDE

Step 0: See if your IDE has Maven Embedded

If you use Eclipse:

1. Go to Window → Preferences
2. On the left hand side, double click Maven and then click Installations
3. If there is an option that says EMBEDDED, then Maven is already part of your IDE. You should be able to see the version number under “Details”

If you use IntelliJ:

1. Go to File → Settings
2. Click on “Build, Execution, Deployment” in the left hand panel
3. Double click on Build → Build Tools → Maven
4. The “maven home directory” should show you where the Maven install is located, the version, and whether it is bundled with your IntelliJ install

If you don’t have Maven installed, you’ll have to follow the rest of the instructions below.

Step 1: Check to see if Maven is already installed

1. Type cmd in the “Start your search” box in the lower left hand corner.
2. At the prompt, type mvn -v
   • If Maven is installed, you’ll see which version you have. Go to Step 4.
   • If you see 'mvn' is not recognized then continue to Step 2.

Step 2: Download Maven

1. Go to https://maven.apache.org/download.cgi
2. Check to see if your JDK is recent enough to support the latest Maven. The instructions at this URL should tell you what to look for. For example, you’ll see something like “Maven 3.3+ requires JDK 1.7 or above to execute.”
3. Type cmd in the “Start your search” box in the lower left hand corner (or, if you already have a cmd window open from Step 1, go back to it)
4. At the prompt, type java -version
5. Check to make sure the JDK version is at least as high as what Maven requires (in this example, 1.7)
6. Unless you know how to handle untarring and unzipping, download the “Binary zip archive” (e.g. apache-maven-3.6.3-bin.zip)
7. Unzip Maven & remember what directory it’s installed in -- write it down.

Step 3: Update Environment Variables

1. Type environment in the “Start your search” box in the lower left hand corner and select “Edit the System Environment Variables” in the Control Panel.
2. Click the “Environment Variables” button in the lower right of the pop-up window.
3. If MAVEN_HOME is not in the “System variables” section, then click “New” (the one that’s down on the bottom)
4. Enter MAVEN_HOME and your full path to Maven (the last instruction from Step 2, above). This example shows the path based on where I installed Maven on my machine:

1. Click OK to commit changes.
2. In “System variables” click the line that starts with “Path”
3. Click “Edit” at the bottom
4. Click “New”
5. Add the full path name to the /bin directory inside your Maven install. You may have to search for bin in the File Explorer window to find it. For example, my full path is C:\Program Files\Java\apache-maven-3.6.3\bin
6. Click OK, and OK again.
7. Now your computer should be able to find Maven… in the next step, we’ll check.

Step 4: Verify Maven Install

Go back to Step 1! Be sure to open a NEW cmd window so your old settings don't mislead you.

Step 4: Connect Maven to Your IDE

If you use EclipseIDE:

• Go to Window → Preferences
• On the left hand side, double click Maven and then click Installations
• Click “Add” and let Eclipse know what directory Maven is installed in

If you use IntelliJ:

• Go to File → Settings
• Click on “Build, Execution, Deployment” in the left hand panel
• Double click on Build → Build Tools → Maven
• Click on the three dots to the right of “Maven home directory” and tell it the path where it can find your new install
• Click OK

-- NicoleRadziwill - 03 Apr 2020

Maven Install on MacOS

Step 1: See if your IDE has Maven Embedded

If you use Eclipse:

1. Go to Eclipse → Preferences
2. On the left hand side, double click Maven and then click Installations
3. If there is an option that says EMBEDDED, then Maven is already part of your IDE. You should be able to see the version number under “Details”

If you use IntelliJ:

1. Go to IntelliJ IDEA → Preferences
2. Click on “Build, Execution, Deployment” in the left hand panel
3. Double click on Build Tools → Maven
4. The “maven home directory” should show you where the Maven install is located, the version, and whether it is bundled with your IntelliJ install

If you don’t have Maven installed, you’ll have to follow the rest of the instructions below.

Step 2: Check to see if Maven is already installed

NOTE: Since 10.6.8 MacOSx Snow Leopard, Mac OS X comes with Apache Maven 3 built in.

1. Open your Terminal.
2. At the prompt, type mvn -v
   • If Maven is installed, you’ll see which version you have. Go to Step 4.
   • If you see 'mvn' is not recognized then continue to Step 3.

Step 3: Download Maven

1. Go to https://maven.apache.org/download.cgi
2. Check to see if your JDK is recent enough to support the latest Maven. The instructions at this URL should tell you what to look for. For example, you’ll see something like “Maven 3.3+ requires JDK 1.7 or above to execute.”
3. Open Terminal, type java -version
4. Check to make sure the JDK version is at least as high as what Maven requires (in this example, 1.7)
5. Unless you know how to handle untarring and unzipping, download the “Binary zip archive” (e.g. apache-maven-3.6.3-bin.zip)
6. Unzip Maven to your desired location.

Step 4: Update Environment Variables

1. Open Terminal
   • This next step requires some vi editing knowledge
2. Type vi ~/.bash_profile
3. Type i for insert
4. Arrow down to below the last export line
5. Enter the following
   

   M2_HOME=/usr/local/apache-maven-3.5.2
   PATH=$PATH:$M2_HOME/bin

6. Click ESC to exit insert mode
7. type :wq (w = write, q = quit) to save and close
8. For the changes to take effect, you need to refresh your profile
   Type source ~/.bash_profile

Step 5: Verify Maven Install

Go back to Step 2! Be sure to open a NEW terminal window so your old settings don't mislead you.

-- MichaelComstock - 24 Sep 2020