Maven Repositories: Local, Central, and Remote

Direct Answer

Maven resolves artifacts through a local repository on the developer machine and configured remote repositories. Maven Central is the default public remote in Maven's standard setup; a company Nexus or Artifactory server is another remote and may proxy Central. Central is not a third repository category—it is one remote repository.

Code Example

<!-- pom.xml - configuring custom remote repository -->
<project>
    <repositories>
        <!-- Company Nexus proxy for faster builds -->
        <repository>
            <id>company-nexus</id>
            <url>https://nexus.company.com/repository/maven-public</url>
        </repository>
    </repositories>
    
    <dependencies>
        <!-- Maven checks: ~/.m2 -> Nexus -> Central -->
        <dependency>
            <groupId>com.company</groupId>
            <artifactId>internal-utils</artifactId>
            <version>2.1.0</version>
        </dependency>
        
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
            <version>3.2.0</version>
        </dependency>
    </dependencies>
</project>

Common Mistakes & Pitfalls

• Deleting the .m2 directory thinking it's temporary: Freshers see ~/.m2 taking gigabytes and delete it, then wonder why Maven re-downloads every dependency on the next build. It's a cache that should persist.
• Not understanding the resolution order: They don't realize Maven checks local first, so an offline build can work when every dependency, plugin, parent, and required metadata item is already local.
• Ignoring repository managers in companies: They hardcode Maven Central URLs instead of using the company Nexus, bypassing security scans and slower builds when Central is slow.