Master Maven: Complete Guide to Java Build Automation and Project Management

Introduction

All current company projects use Maven, but many developers have not had time to study it. This article provides a detailed, step‑by‑step guide.

Why Use Maven

Large projects benefit from splitting into multiple modules (each module as a separate Maven project) for better collaboration.

JAR dependencies are stored in a central repository, eliminating repetitive copy‑paste.

Maven automates downloading of JARs from remote repositories.

It prevents version conflicts by sharing a single JAR copy across projects.

Transitive dependencies are resolved automatically.

What Is Maven

Maven is an automated build tool for the Java platform. It follows the evolution: make → Ant → Maven → Gradle. Maven handles compilation, testing, packaging, and deployment.

Installation

Ensure JAVA_HOME is set.

Download Maven and extract it to a directory without spaces or non‑ASCII characters.

Add M2_HOME (the Maven root directory) and %M2_HOME%\bin to the system PATH.

Verify installation with mvn -v.

First Maven Project

Create the standard Maven directory layout:

project-root/
├─ src/main/java   (source code)
├─ src/main/resources (configuration files)
├─ src/test/java   (test code)
└─ pom.xml          (project descriptor)

Add a simple Java class Hello.java and a minimal pom.xml with a JUnit dependency.

Common Maven Commands

mvn clean

– remove previous build output. mvn compile – compile main sources. mvn test-compile – compile test sources. mvn test – run unit tests. mvn package – create a JAR/WAR. mvn install – install the artifact into the local repository.

All commands must be executed from the directory containing pom.xml.

Repository and Coordinates

The pom.xml is the Project Object Model file that defines the project. Maven coordinates ( groupId:artifactId:version) uniquely identify an artifact in a repository. Maven stores artifacts in a local repository (default C:\Users\<username>\.m2\repository) and can retrieve missing artifacts from remote repositories (central or private Nexus servers).

Dependency Management

Maven first looks in the local repository; if not found, it downloads from the remote repository.

For internal projects, run mvn install on the dependency project to publish its JAR to the local repository.

Dependency scopes control where a dependency is available (compile, provided, runtime, test, system).

Lifecycle

Maven defines three independent lifecycles:

Clean – pre‑clean, clean, post‑clean.

Default – validate, compile, test, package, install, deploy, etc.

Site – generate project documentation and site.

Each phase executes associated plugins.

Using Maven in Eclipse

Open Window → Preferences → Maven → Installations and add the extracted Maven directory.

Set the user settings.xml to configure the local repository path if needed.

Create a Maven project via File → New → Maven Project and follow the wizard.

Adjust project facets, JDK version, and add required libraries (e.g., Tomcat) through project properties.

Advanced Dependency Features

Transitive dependencies propagate automatically, except for non‑compile scopes.

Version conflict resolution follows the “shortest path first” and “first declaration wins” rules.

Centralized version management can be achieved using <properties> in the parent POM.

Build Configuration

<build>
  <finalName>WebMavenDemo</finalName>
  <resources>
    <resource>
      <directory>src/main/java</directory>
      <includes><include>**/*.xml</include></includes>
    </resource>
  </resources>
  <plugins>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <version>2.1</version>
      <configuration>
        <source>1.8</source>
        <target>1.8</target>
      </configuration>
    </plugin>
    ... (other plugins) ...
  </plugins>
</build>

Running mvn package generates the configured WAR/JAR in the target directory.

Conclusion

The article has covered Maven’s core concepts, installation, project setup, commands, repository handling, dependency scopes, lifecycles, Eclipse integration, and advanced features, providing a solid foundation for using Maven in Java development.