The specific goals bound to each phase default to a set of
goals specific to a project's packaging. A project with packaging
jar has a different set of default goals from a project
with a packaging of war. The
packaging element affects the steps required to build a
project. For an example of how the packaging affects the build, consider
two projects: one with pom packaging and the other with
jar packaging. The project with pom
packaging will run the site:attach-descriptor goal
during the package phase, and the project with
jar packaging will run the jar:jar
goal instead.
The following sections describe the lifecycle for all built-in packaging types in Maven. Use these sections to find out what default goals are mapped to default lifecycle phases.
JAR is the default packaging type, the most common, and thus the most commonly encountered lifecycle configuration. The default goals for the JAR lifecycle are shown in Table 4.2, “Default Goals for JAR Packaging”.
Table 4.2. Default Goals for JAR Packaging
| Lifecycle Phase | Goal |
|---|---|
| process-resources | resources:resources |
| compile | compiler:compile |
| process-test-resources | resources:testResources |
| test-compile | compiler:testCompile |
| test | surefire:test |
| package | jar:jar |
| install | install:install |
| deploy | deploy:deploy |
