Skip to content

maven.md

Latest commit

 

History

History
68 lines (48 loc) · 3.9 KB

maven.md

File metadata and controls

68 lines (48 loc) · 3.9 KB
Raw

What is Apache Maven?

At its core, Apache Maven is a powerful project management and comprehension tool. While many people think of it simply as a tool to "build" code, it actually manages the entire lifecycle of a software project—from compilation and testing to packaging and deployment.

It is based on the concept of a Project Object Model (POM). Instead of writing complex scripts to tell the computer how to build your project, you describe what your project looks like in an XML file (pom.xml), and Maven handles the rest.

Why Do We Need It?

Before Maven (and similar tools), developers had to manage libraries manually. If your project needed a specific library, you had to:

  1. Find the JAR file online.
  2. Download it.
  3. Add it to your project’s classpath.
  4. Realize that library needed three other libraries to work (Transitive Dependencies) and go find those, too.

Key Problems Maven Solves:

  • Dependency Management: Maven automatically downloads the libraries your project needs from a central repository.
  • Standardized Project Structure: Every Maven project follows the same folder layout (e.g., src/main/java for code, src/test/java for tests). This makes it easy for a new developer to jump into any project and know exactly where everything is.
  • Automation: It automates repetitive tasks like compiling code, running unit tests, and creating a JAR or WAR file.

The Core Components

1. The pom.xml File

The heart of every Maven project. It contains:

  • Artifact ID & Group ID: The unique "coordinates" for your project.
  • Dependencies: A list of external libraries.
  • Plugins: Extra tools for tasks like code coverage or minification.

2. Repositories

  • Local Repository: A folder on your machine (usually ~/.m2) where Maven stores downloaded JARs so it doesn't have to download them again.
  • Central Repository: An online library provided by the Maven community containing millions of JAR files.

3. The Build Lifecycle

Maven works through a sequence of "phases." If you run a later phase, all previous phases run automatically.

  • validate: Check if the project is correct.
  • compile: Turn .java files into .class files.
  • test: Run unit tests (like JUnit).
  • package: Wrap the compiled code into a JAR/WAR.
  • install: Put the package into your local repository (so other local projects can use it).

Why Maven Over Others (Ant or Gradle)?

Feature Ant Maven Gradle
Philosophy "Tell me exactly how to do it." (Procedural) "Tell me what the project is." (Declarative) "Tell me what the project is, but let me code exceptions."
Ease of Use Difficult; requires long XML scripts. High; uses "Convention over Configuration." High; uses a flexible DSL (Groovy/Kotlin).
Dependency Mgmt None (unless using Ivy). Excellent and built-in. Excellent and highly customizable.
Performance Fast, but manual. Standard. Fastest (uses incremental builds).

Why choose Maven specifically?

  1. Strict Standards: Because Maven enforces a structure, it’s great for large teams. You don't have to guess how someone else set up their build script.
  2. Maturity: It has been the industry standard for Java for over a decade. Most enterprise plugins and tools are built for Maven first.
  3. Low Learning Curve: For 90% of projects, you just copy-paste a dependency snippet into your pom.xml and it "just works."

Everything You Need to Know (Summary)

  • Convention over Configuration: Don't fight the folder structure; follow it, and Maven does the work for you.
  • Transitive Dependencies: If you include Spring Boot, Maven automatically pulls in all the sub-libraries Spring Boot needs.
  • Scope: You can tell Maven to use a library only for testing (test) or only during compilation (provided), keeping your final file small.