For example, package executes jar:jar if the project type is a JAR, and war:war if the project type is - you guessed it - a WAR.Īn interesting thing to note is that phases and goals may be executed in sequence. The specific goals executed per phase is dependant upon the packaging type of the project. Phases are actually mapped to underlying goals. site: generates site documentation for this project.clean: cleans up artifacts created by prior builds.There are two other Maven lifecycles of note beyond the default list above. deploy: done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.
#MAVEN INSTALL JAR LOCALLY INSTALL#
![maven install jar locally maven install jar locally](https://i2.wp.com/img-blog.csdnimg.cn/20200429165137617.png)
![maven install jar locally maven install jar locally](https://i0.wp.com/laatstewashington.com/eqc/980oUmm9E8E.jpeg)
This archetype:generate goal created a simple project based upon a maven-archetype-quickstart archetype.
![maven install jar locally maven install jar locally](https://robinhowlett.com/assets/images/posts/2019/multi-module-layout.png)
If you are familiar with Ant, you may conceive of this as similar to a task. The prefix archetype is the plugin that provides the goal. You executed the Maven goal archetype:generate, and passed in various parameters to that goal.