Master Maven: From Repositories to Lifecycle in One Guide

Preface

In modern Java projects Maven is ubiquitous; its repository management, dependency handling, inheritance, and aggregation give a complete solution for building multi‑module projects. Without understanding Maven you may face painful dependency conflicts and unclear project execution.

Thinking in Maven

When you join a new company you typically install JDK, configure MAVEN_HOME and PATH, and often edit settings.xml to set a local repository path or private server configuration. After configuring the IDE (IDEA/Eclipse) you add <dependency> tags in pom.xml, write code following Maven’s standard directory layout, and use plugins to test, package (jar/war), deploy, and run.

Q1: Local repository and Maven repositories

A local repository acts as a cache for JARs; if a JAR is not found locally Maven checks the private server (private repository) and finally the central repository ( http://repo1.maven.org/maven2/). The private repository is a company‑internal server that stores internal JARs and can act as a mirror of the central repository.

Q2: Using <dependency>

The <dependency> tag defines the coordinates of a JAR: groupId, artifactId, and version. You can search for coordinates on search.maven.org or mvnrepository.com. Versions are either Snapshot (development) or Release (stable); snapshots allow automatic updates of the latest timestamped build.

Q3: Dependency conflicts and their resolution

Maven permits only one version per groupId / artifactId. The version that appears nearest to the project in the dependency tree is used, which can cause runtime errors if transitive dependencies bring incompatible versions. To resolve conflicts you can:

Lock a specific version using <dependencyManagement>.

Exclude unwanted transitive dependencies with <exclusions>.

Declare an explicit <dependency> with the desired version.

Q4: Best practice for adding dependencies

Before adding a new dependency, run mvn dependency:tree to view the full dependency graph, check for transitive dependencies, and detect version conflicts early.

Q5: Maven’s standard directory structure

Under src/main the code and resources are packaged into the final JAR/WAR, while src/test contains test code that is not packaged. Files in src/main/resources are copied to the output directory, which is required for frameworks like MyBatis or Hibernate.

Q6: Maven lifecycle

The most common lifecycle phases are:

clean : removes previous build artifacts.

package : creates a JAR/WAR and implicitly runs clean and compile.

install : installs the built artifact into the local repository.

deploy : uploads the artifact to a remote repository.

Q7: Dependency scopes

Different scopes control when a dependency is available:

compile (default): needed at runtime and packaged.

provided : needed for compilation but supplied by the runtime container (e.g., servlet-api).

runtime : not needed for compilation but required at runtime (e.g., JDBC driver).

test : only for test code, not packaged.

system : external JARs referenced by an absolute path (rarely used).