Mobile App Development - Maven

Back to Course

Lesson Description

Lession - #408 Maven Default Lifecycle

The default lifecycle involves the following stages (for a complete list of the lifecycle stages, refer to the Lifecycle Reference>

validate - Validate the project is correct and all necessary data is accessible

compile - compile the source code of the project

test - test the compiled source code utilizing a suitable unit testing framework. These tests should not require the code be packaged or deployed.

package - take the compiled code and package it in its distributable format, like a JAR.

verify - run any checks on results of integration tests to guarantee quality standards are met

install - install the package into the local repository, for use as a dependency in different projects locally

deploy - done in the build environment, duplicates the final package to the remote repository for sharing with other developers and projects.

These lifecycle phases (in addition to the next lifecycle phases not displayed here>
are executed consecutively to finish the default lifecycle. Given the lifecycle stages over, this implies that when the default lifecycle is utilized, Maven will initially approve the task, then, at that point, will attempt to accumulate the sources, run those against the tests, package the binaries (for example jar>
, run integration tests against that bundle, confirm the incorporation tests, introduce the checked bundle to the neighborhood store, then, to the local repository, deploy the installed package to a remote repository.

Default life cycle