Master Maven: 7 Essential Questions Every Java Developer Should Know

1. Maven Repositories: Local, Private, and Central

Maven uses a hierarchy of repositories. The local repository caches downloaded artifacts; if not found, Maven checks the private (company) repository, and finally the central repository (http://repo1.maven.org/maven2/). This layered approach reduces network traffic and speeds up builds.

The local repository path can be configured in settings.xml. Private repositories act as mirrors of the central repository and store internal company artifacts.

2. Using the <dependency> Tag

Dependencies are defined with <dependency>, specifying groupId , artifactId , and version . Versions can be snapshots (development) or releases (stable). Snapshots include timestamps, allowing automatic updates of the latest build.

3. Why Dependency Conflicts Occur and How to Resolve Them

Conflicts arise when different modules depend on different versions of the same artifact. Maven applies a "nearest" strategy, using the version closest to the project in the dependency tree. To control conflicts, you can:

Define versions centrally with <dependencyManagement> for multi‑module consistency.

Exclude transitive dependencies using <exclusions>.

Declare explicit versions directly in <dependency>.

4. Best Practice: Detect Problems Early

Before adding a new dependency, run mvn dependency:tree to view the full dependency graph, identify transitive dependencies, and spot version clashes. Resolve any issues using the techniques above.

5. Maven Standard Directory Layout

Key points:

src/main contains production code and resources packaged into the final JAR/WAR.

src/test holds test code, which is not packaged.

Resources under src/main/resources are copied to the output directory.

6. Maven Build Lifecycle

Common commands:

clean : remove previous build artifacts.

package : compile and package the code into a JAR/WAR.

install : place the artifact into the local repository.

deploy : upload the artifact to a remote repository.

7. Dependency Scopes

Scopes control when a dependency is available:

compile (default): needed at compile and runtime, packaged.

provided : needed at compile time but supplied by the runtime environment, not packaged.

runtime : not needed for compilation, required at runtime, packaged.

test : only for testing, not packaged.

system : external JARs referenced by absolute path, rarely used.