![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/human-life-cycle.jpg\")
<\/figure>\n\n\n\nSoftware Development Life Cycle<\/h3>\n\n\n\n![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/6_phases_of_software_development_life_cycle-1024x554.png\")
<\/figure>\n\n\n\nBuild Lifecycle in Maven for Managing Software Build Process<\/h2>\n\n\n\n
Maven is based around the central concept of a build lifecycle. What this means is that the process for building and distributing a particular artifact (project) is clearly defined.<\/p>\n\n\n\n
For the person building a project, this means that it is only necessary to learn a small set of commands to build any Maven project, and the POM<\/a> will ensure they get the results they desired.<\/p>\n\n\n\nThere are three built-in build lifecycles: default, clean and site. The default<\/code> lifecycle handles your project deployment, the clean<\/code> lifecycle handles project cleaning, while the site<\/code> lifecycle handles the creation of your project’s web site.<\/p>\n\n\n\nMaven defines 3 lifecycles in META-INF\/plexus\/components.xml:<\/p>\n\n\n\n
- default Lifecycle<\/a><\/li>
- clean Lifecycle<\/a><\/li>
- site Lifecycle<\/a><\/li><\/ul>\n\n\n\n
![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/maven-lifecycle-phase-goal-1024x534.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/image-37-1024x505.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/image-38.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/image-39-1024x363.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/mvn-plugins-package-goals.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/Maven_LifeCycle_Table.png\")
<\/figure>\n\n\n\nEach of these build lifecycles is defined by a different list of build phases, wherein a build phase represents a stage in the lifecycle.<\/p>\n\n\n\n
For example, the default lifecycle comprises of the following phases (for a complete list of the lifecycle phases, refer to the Lifecycle Reference<\/a>):<\/p>\n\n\n\nvalidate<\/code> – validate the project is correct and all necessary information is available<\/li>compile<\/code> – compile the source code of the project<\/li>test<\/code> – test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed<\/li>package<\/code> – take the compiled code and package it in its distributable format, such as a JAR.<\/li>verify<\/code> – run any checks on results of integration tests to ensure quality criteria are met<\/li>install<\/code> – install the package into the local repository, for use as a dependency in other projects locally<\/li>deploy<\/code> – done in the build environment, copies the final package to the remote repository for sharing with other developers and projects.<\/li><\/ul>\n\n\n\nThese lifecycle phases (plus the other lifecycle phases not shown here) are executed sequentially to complete the\u00a0default<\/code>\u00a0lifecycle. Given the lifecycle phases above, this means that when the default lifecycle is used, Maven will first validate the project, then will try to compile the sources, run those against the tests, package the binaries (e.g. jar), run integration tests against that package, verify the integration tests, install the verified package to the local repository, then deploy the installed package to a remote repository.<\/p>\n\n\n\n![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/Maven-Life-Cycle-1.jpg\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/image-40-1024x437.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2022\/09\/image-41.png\")
<\/figure>\n\n\n\nLifecycle Reference<\/h2>\n\n\n\n
The following lists all build phases of the default<\/code>, clean<\/code> and site<\/code> lifecycles, which are executed in the order given up to the point of the one specified.<\/p>\n\n\n\n<\/a>Clean Lifecycle<\/a><\/h3>\n\n\n\n
<\/figure>\n\n\n\nBuild Lifecycle in Maven for Managing Software Build Process<\/h2>\n\n\n\n
Maven is based around the central concept of a build lifecycle. What this means is that the process for building and distributing a particular artifact (project) is clearly defined.<\/p>\n\n\n\n
For the person building a project, this means that it is only necessary to learn a small set of commands to build any Maven project, and the POM<\/a> will ensure they get the results they desired.<\/p>\n\n\n\n There are three built-in build lifecycles: default, clean and site. The Maven defines 3 lifecycles in META-INF\/plexus\/components.xml:<\/p>\n\n\n\n Each of these build lifecycles is defined by a different list of build phases, wherein a build phase represents a stage in the lifecycle.<\/p>\n\n\n\n For example, the default lifecycle comprises of the following phases (for a complete list of the lifecycle phases, refer to the Lifecycle Reference<\/a>):<\/p>\n\n\n\n These lifecycle phases (plus the other lifecycle phases not shown here) are executed sequentially to complete the\u00a0 The following lists all build phases of the default<\/code> lifecycle handles your project deployment, the clean<\/code> lifecycle handles project cleaning, while the site<\/code> lifecycle handles the creation of your project’s web site.<\/p>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\nvalidate<\/code> – validate the project is correct and all necessary information is available<\/li>compile<\/code> – compile the source code of the project<\/li>test<\/code> – test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed<\/li>package<\/code> – take the compiled code and package it in its distributable format, such as a JAR.<\/li>verify<\/code> – run any checks on results of integration tests to ensure quality criteria are met<\/li>install<\/code> – install the package into the local repository, for use as a dependency in other projects locally<\/li>deploy<\/code> – done in the build environment, copies the final package to the remote repository for sharing with other developers and projects.<\/li><\/ul>\n\n\n\ndefault<\/code>\u00a0lifecycle. Given the lifecycle phases above, this means that when the default lifecycle is used, Maven will first validate the project, then will try to compile the sources, run those against the tests, package the binaries (e.g. jar), run integration tests against that package, verify the integration tests, install the verified package to the local repository, then deploy the installed package to a remote repository.<\/p>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\nLifecycle Reference<\/h2>\n\n\n\n
default<\/code>, clean<\/code> and site<\/code> lifecycles, which are executed in the order given up to the point of the one specified.<\/p>\n\n\n\n<\/a>Clean Lifecycle<\/a><\/h3>\n\n\n\n