Apache Maven

Apache Maven standardizes how a Java project is built, tested, packaged, documented, and distributed. Its central aim is convention over configuration: a project can obtain predictable behavior by following conventional directory names and lifecycle phases rather than declaring every command manually.¹ Maven emerged from work on the Jakarta Alexandria project and became an Apache top-level project in the early 2000s, addressing recurring complexity in large Java builds.

The tool is distinct from a compiler or an integrated development environment. Maven coordinates those components through plugins, while the Java compiler, test frameworks, packaging tools, and documentation generators perform specialized tasks. Its model also makes a build portable across development machines and continuous-integration environments, provided the required repositories and tool versions are available.

The Project Object Model, usually called the POM, is Maven's declarative description of a project. A pom.xml records coordinates such as groupId, artifactId, and version, along with packaging, dependencies, plugins, properties, and inheritance relationships.² A project's coordinates identify its published artifact in a repository.

Maven resolves a dependency graph rather than merely downloading a named file. Transitive dependencies are included automatically, while mediation rules select versions when paths conflict; scopes such as compile, test, and provided limit where dependencies participate.³ Artifacts may come from a local repository, a configured remote repository, or a repository mirror. Explicit versions, dependency management, and reproducible repository policies remain important because automatic resolution can otherwise change a build's effective inputs.

Maven organizes work into lifecycles made of ordered phases, so invoking a later phase also executes the earlier phases required to reach it. The standard default lifecycle includes phases such as validate, compile, test, package, verify, install, and deploy.⁴ Commands such as mvn test and mvn package therefore express goals at a higher level than individual shell scripts.

Plugins implement the work attached to lifecycle phases. The compiler, Surefire test runner, JAR packager, and site generator are examples of plugin responsibilities, and a project can configure their goals in its POM.¹ Multi-module builds use a parent POM and a reactor to build related modules in dependency order. This supports shared configuration, although excessive inheritance or implicit plugin behavior can make large builds difficult to diagnose.

Maven's lesser-known features include profiles, repositories, and a separate reporting model. Profiles can activate alternate properties, dependencies, or plugin settings by operating system, JDK, property, or explicit command-line selection; they are useful for legitimate environment differences but can reduce reproducibility when activation is opaque.²

Packaging is not limited to a simple Java archive. Maven supports project types and custom lifecycle mappings through packaging extensions, while the site lifecycle can produce project documentation and reports independently of the binary build.⁴ Maven also supports parallel module execution, though plugins and generated files must be safe for concurrent work. The Maven Wrapper is a companion mechanism that lets a repository specify and download the Maven distribution needed by a project, reducing differences between local and automated environments.

Maven is widely used as a boundary between source code and delivery systems: continuous-integration services can invoke the same lifecycle commands used by developers, and repositories can retain versioned artifacts for later builds. Its standard metadata enables IDEs, code-quality tools, release systems, and dependency scanners to inspect a project without understanding bespoke shell scripts.

The model has trade-offs. A large dependency graph can introduce version conflicts, lengthy downloads, or supply-chain risk, and a build may depend on network availability unless artifacts are cached or mirrored. Teams commonly address these issues with locked-down repositories, explicit plugin versions, dependency analysis, checksums, and isolated build environments. Maven remains especially influential because its conventions and POM metadata became a shared vocabulary across the Java ecosystem rather than merely a collection of command-line tasks.

POM

Project Object Model; the XML descriptor that defines a Maven project's coordinates, dependencies, build configuration, and metadata.

Artifact

A versioned file or publication, such as a JAR, POM, or source archive, identified by Maven coordinates.

Lifecycle phase

A named stage in an ordered Maven lifecycle, such as compile, test, package, or deploy.

Plugin goal

A specific operation supplied by a Maven plugin and bound to, or invoked from, a lifecycle phase.

Reactor

Maven's mechanism for building a set of related modules in an order derived from their interdependencies.