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

Post a Comment

Popular posts from this blog

Example of Maven project that interacts with a MySQL database and includes testing

Example Maven project that interacts with a MySQL database and includes testing To install Java, MySQL, Maven, and write a Java program to fetch table data, execute, and create a JAR file using Maven on Ubuntu, you can follow these steps: Step 1: Install Java You can install Java using the following commands: sudo apt update sudo apt install default-jre sudo apt install default-jdk Verify the installation by running: java -version Step 2: Install MySQL You can install MySQL using the following commands: sudo apt update sudo apt install mysql-server During the installation, you'll be prompted to set a root password for MySQL or you can set password at latter stage using following steps.  sudo mysql ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password'; exit Step 3: Install Maven You can install Maven using the following commands: sudo apt update sudo apt install maven Verify the installation by running: mvn -version Step 4: Create
Post a Comment
Read more

Maven Create and Build Artifacts

In Maven, you can create and build artifacts using the package phase of the build lifecycle. The package phase is responsible for taking the compiled code and other project resources and packaging them into a distributable format, such as a JAR (Java Archive), WAR (Web Application Archive), or other custom formats. Here are the steps to create and build artifacts using Maven: Configure the Build Output: In your project's pom.xml file, you need to configure the output of the build. This includes specifying the type of artifact you want to create (e.g., JAR, WAR) and any additional resources to include. You do this in the <build> section of your pom.xml: <build>     <finalName>my-artifact</finalName> <!-- Name of the artifact without the extension -->     <plugins>         <!-- Plugin configurations for creating the artifact -->         <!-- For example, maven-jar-plugin or maven-war-plugin -->     </plugins> </build> Depend
Post a Comment
Read more

Maven Repositories (local, central, global)

Maven relies on repositories to manage dependencies, plugins, and other artifacts required for a project. There are typically three types of repositories in Maven: local, central, and remote/global repositories. Local Repository: Location: The local repository is located on your local development machine. By default, it's in the .m2 directory within your user home directory (e.g., C:\Users\<username>\.m2\repository on Windows or /Users/<username>/.m2/repository on macOS and Linux). Purpose: The local repository is used to store artifacts (JARs, POMs, and other files) that your machine has downloaded or built during previous Maven builds. These artifacts are specific to your local development environment. Benefits: Using a local repository improves build performance since it caches dependencies locally, reducing the need to download them repeatedly. It also ensures reproducibility by maintaining a local copy of dependencies. Central Repository: Location: The central repo
Post a Comment
Read more