Common Maven Interview Questions and Essential Practices

Maven is a widely used build automation tool in Java projects, offering repository management, dependency management, inheritance, and aggregation.

Repository Types

Explain local repository (cache), private (company) repository acting as a mirror, and central repository (http://repo1.maven.org/maven2/). Local repository stores downloaded artifacts; if not found, Maven searches the private repository, then the central repository, syncing artifacts back.

Dependency Declaration

The <dependency> element defines groupId, artifactId, and version. Versions can be snapshots (development) or releases (stable). Snapshot versions are timestamped and automatically updated during builds.

Dependency Conflicts

Conflicts arise when different transitive dependencies require different versions of the same artifact. Maven uses the nearest-wins strategy in the dependency tree. Resolution methods include using <dependencyManagement> for version alignment, <exclusions> to remove unwanted transitive dependencies, and explicitly declaring the desired version.

Best Practices

Before adding a new dependency, run mvn dependency:tree to inspect transitive dependencies and detect version clashes, then apply the above strategies.

Standard Directory Structure

src/main contains production code packaged into JAR/WAR; src/test holds test code not packaged. Resources under src/main/resources are copied to the output directory.

Lifecycle

Maven defines phases such as clean, compile, test, package, install, and deploy; invoking a later phase automatically runs preceding phases.

Scope

Scopes control dependency availability: compile (default, included in the package), provided (available at compile time but not packaged), runtime (needed at runtime only), test (used only for testing), and system (explicit path, rarely used).