Skip to main content

Maven Build lifecycle

Maven follows a predefined and well-defined build lifecycle that consists of a series of phases and goals. Each phase represents a specific step in the build process, and within each phase, one or more goals are executed. The build lifecycle ensures that project compilation, testing, packaging, and deployment tasks are carried out in a consistent and standardized manner. The three main build lifecycles in Maven are:


Default Build Lifecycle:

The default build lifecycle is the most commonly used and consists of the following phases:

  1. validate: Validates the project's structure and configuration.
  2. compile: Compiles the source code of the project.
  3. test: Executes unit tests using a suitable unit testing framework (e.g., JUnit).
  4. package: Packages the compiled code into a distributable format, such as a JAR or WAR.
  5. verify: Runs any checks on the results of integration tests to ensure the quality of the build.
  6. install: Installs the packaged artifact into the local repository for use as a dependency in other projects.
  7. deploy: Deploys the final artifact to a remote repository for sharing with other developers or projects.


Clean Build Lifecycle:

The clean build lifecycle is responsible for cleaning up artifacts created during the build process. It consists of the following phases:

  1. pre-clean: Executes any necessary tasks before the project is cleaned.
  2. clean: Deletes all files generated by the previous build.
  3. post-clean: Executes any necessary tasks after the project is cleaned.


Site Build Lifecycle:

The site build lifecycle is used to generate a project's site documentation. It consists of the following phases:

  1. pre-site: Executes any necessary tasks before generating the site documentation.
  2. site: Generates the site documentation for the project.
  3. post-site: Executes any necessary tasks after generating the site documentation.
  4. site-deploy: Deploys the generated site documentation to a remote repository or server.

To execute a specific phase of a build lifecycle, you use the mvn command followed by the phase name. For example, to compile the project, you run mvn compile, and to package the project, you run mvn package. By running one phase, all preceding phases in the lifecycle will be executed automatically.


Maven plugins are used to implement the goals associated with each phase. Maven's build lifecycle and plugin architecture make it easy to build and manage complex projects with consistent and repeatable build processes. Developers can customize the build process by configuring plugins, but the default lifecycle is usually sufficient for most projects.

Comments

Popular posts from this blog

Experiment No. 5 Title: Applying CI/CD Principles to Web Development Using Jenkins, Git, and Local HTTP Server

  Experiment No. 5 Title: Applying CI/CD Principles to Web Development Using Jenkins, Git, and Local HTTP Server  Objective: The objective of this experiment is to set up a CI/CD pipeline for a web development project using Jenkins, Git, and webhooks, without the need for a Jenkinsfile. You will learn how to automatically build and deploy a web application to a local HTTP server whenever changes are pushed to the Git repository, using Jenkins' "Execute Shell" build step. Introduction: Continuous Integration and Continuous Deployment (CI/CD) is a critical practice in modern software development, allowing teams to automate the building, testing, and deployment of applications. This process ensures that software updates are consistently and reliably delivered to end-users, leading to improved development efficiency and product quality. In this context, this introduction sets the stage for an exploration of how to apply CI/CD principles specifically to web development using J

Experiment No. 6 Title: Exploring Containerization and Application Deployment with Docker

  Experiment No. 6 Title: Exploring Containerization and Application Deployment with Docker  Objective: The objective of this experiment is to provide hands-on experience with Docker containerization and application deployment by deploying an Apache web server in a Docker container. By the end of this experiment, you will understand the basics of Docker, how to create Docker containers, and how to deploy a simple web server application. Introduction Containerization is a technology that has revolutionised the way applications are developed, deployed, and managed in the modern IT landscape. It provides a standardised and efficient way to package, distribute, and run software applications and their dependencies in isolated environments called containers. Containerization technology has gained immense popularity, with Docker being one of the most well-known containerization platforms. This introduction explores the fundamental concepts of containerization, its benefits, and how it differs

Experiment No. 10 Title: Create the GitHub Account to demonstrate CI/CD pipeline using Cloud Platform.

  Experiment No. 10 Title: Create the GitHub Account to demonstrate CI/CD pipeline using Cloud Platform. Objective: The objective of this experiment is to help you create a GitHub account and set up a basic CI/CD pipeline on GCP. You will learn how to connect your GitHub repository to GCP, configure CI/CD using Cloud Build, and automatically deploy web pages to an Apache web server when code is pushed to your repository. Introduction: Continuous Integration and Continuous Deployment (CI/CD) pipelines are essential for automating the deployment of web applications. In this experiment, we will guide you through creating a GitHub account and setting up a basic CI/CD pipeline using Google Cloud Platform (GCP) to copy web pages for an Apache HTTP web application. Continuous Integration and Continuous Deployment (CI/CD) is a crucial practice in modern software development. It involves automating the processes of code integration, testing, and deployment to ensure that software changes are co