#Cannot create compile dark basic pro install#
install - install the package into the local repository, for use as a dependency in other projects locally.verify - run any checks on results of integration tests to ensure quality criteria are met.package - take the compiled code and package it in its distributable format, such as a JAR.These tests should not require the code be packaged or deployed test - test the compiled source code using a suitable unit testing framework.compile - compile the source code of the project.validate - validate the project is correct and all necessary information is available.A Build Lifecycle is Made Up of PhasesĮach of these build lifecycles is defined by a different list of build phases, wherein a build phase represents a stage in the lifecycle.įor example, the default lifecycle comprises of the following phases (for a complete list of the lifecycle phases, refer to the Lifecycle Reference): The default lifecycle handles your project deployment, the clean lifecycle handles project cleaning, while the site lifecycle handles the creation of your project's web site. There are three built-in build lifecycles: default, clean and site. What this means is that the process for building and distributing a particular artifact (project) is clearly defined.įor 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 will ensure they get the results they desired. Maven is based around the central concept of a build lifecycle. Setting Up Your Project to Use the Build Lifecycle.Introduction to the Build Lifecycle Table Of Contents