Q3. Maven lifecycle?

The Maven lifecycle defines a structured and standardized process to build, test, package, and deploy an application. In production environments, the Maven lifecycle ensures consistent, repeatable, and automated builds across teams and CI/CD pipelines.

Maven has three built-in lifecycles:

---

1. Clean Lifecycle

Used to clean previous build artifacts before starting a new build.

Phases:

• pre-clean

• clean

• post-clean

Most Used Command:

What it does:

• Deletes the target/ directory

• Removes compiled classes and packaged artifacts

Production Importance:

Ensures no old build artifacts interfere with new builds.
In CI pipelines, we always start with mvn clean to avoid inconsistent builds.

---

2. Default Lifecycle (Main Build Lifecycle)

This is the most important lifecycle used in real projects.

It handles the entire build process from validation to deployment.

Main Phases in Order:

1. validate
   Checks if the project structure is correct.

2. compile
   Compiles source code.

3. test
   Runs unit tests.

4. package
   Creates artifact (JAR/WAR).

5. verify
   Runs integration tests and quality checks.

6. install
   Installs artifact into local Maven repository (~/.m2).

7. deploy
   Deploys artifact to remote repository (Nexus/Artifactory).

---

Common Production Commands:

Builds the application and creates JAR/WAR.

Builds and stores artifact locally.

Builds and pushes artifact to remote repository.

---

Important Concept:

If you run:

Maven automatically runs:

validate → compile → test → package

It executes all previous phases in sequence.

---

Site Lifecycle

Used to generate project documentation.

Phases:

• pre-site

• site

• post-site

• site-deploy

Command:

Production Use:

Rarely used in CI pipelines but useful for documentation and reporting.

---

How Maven Lifecycle Works in CI/CD

In real DevOps pipelines:

CI Flow:

1. Developer pushes code

2. Jenkins/GitHub Actions triggers build

3. Maven runs:

4. If tests pass → artifact packaged

5. Artifact pushed to repository

6. CD pipeline deploys artifact

---

Production Insight

In enterprise environments:

• Unit tests must pass in test phase

• Code coverage tools run during verify

• Sonar analysis integrates during verify phase

• Artifact is immutable after package

• Deploy phase is restricted to release pipelines only

We never allow developers to manually deploy using mvn deploy to production repositories.

---

Interview Advanced Points

Maven Lifecycle is Phase-Based, Not Task-Based

Each phase can have plugins attached.

Example:

• Surefire plugin → test phase

• Jar plugin → package phase

• Deploy plugin → deploy phase

---

Custom Plugins Bind to Lifecycle Phases

Example:

Automatically binds to the test phase.

---

Lifecycle Ensures Build Consistency

Because of standardized lifecycle:

• Any developer machine

• Any CI server

• Any environment

Build behaves the same.

---

Interview Short Answer

“Maven lifecycle defines structured build phases like validate, compile, test, package, install, and deploy. In production CI/CD, we typically run mvn clean verify to ensure clean builds and successful tests before packaging artifacts. Lifecycle ensures repeatable, standardized builds and supports plugin bindings for automation.”