deploy:deploy is used to automatically install the artifact, its pom and the attached artifacts produced by a particular project. Most if not all of the information related to the deployment is stored in the project’s pom. deploy:deploy-file is used to install a single artifact along with its pom.

The Enforcer plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more built-in rules and user created rules.

The Install Plugin is used during the install phase to add artifact(s) to the local repository. The Install Plugin uses the information in the POM (groupId, artifactId, version) to determine the proper location for the artifact within the local repository.

Maven GPG Plugin The maven-gpg-plugin is very handy in this case. With a few lines of configuration, it can help you automatically sign the maven artifacts. With the help of GnuPG and maven-gpg-plugin, you can have more confidence of the security of your Maven artifacts.

The Maven Clean Plugin, as the name implies, attempts to clean the files and directories generated by Maven during its build. While there are plugins that generate additional files, the Clean Plugin assumes that these files are generated inside the target directory.

mvn clean install tells Maven to do the clean phase in each module before running the install phase for each module. What this does is clear any compiled files you have, making sure that you’re really compiling each module from scratch.

In other words, plugins are where much of the real action is performed, plugins are used to: create jar files, create war files, compile code, unit test code, create project documentation, and on and on. Plugins are the central feature of Maven that allow for the reuse of common build logic across multiple projects.

— Apache Maven Install Plugin – Introduction. Having said that, the exact goal purpose: install:install is used to automatically install the project’s main artifact (the JAR, WAR or EAR), its POM and any attached artifacts (sources, javadoc, etc) produced by a particular project.

It’s perfectly safe to delete the folder .

Common Maven Commands

mvn:install copies your packaged Maven module to your local repository (by default, in ~/. m2/repository ), to be accessed by other local Maven builds. mvn:deploy uploads your packaged Maven module to another (usually remote) repository, to be accessed by other, not necessarily local, Maven builds.

So, the answer is yes, mvn deploy will execute install and build the project artifacts.

Maven Enforcer Plugin – The Loving Iron Fist of Maven™ The Enforcer plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more built-in rules and user created rules.

The Enforcer plugin has two goals: enforcer:enforce executes rules for each project in a multi-project build. enforcer:display-info display the current information as detected by the built-in rules.

ENFORCER, a bass plug-in that adds irresistible punch, powerful body and a rigorous low-end bass impulse to your samples. You can heavily beef up sounds or add only a hint of weight. You can use it as a kick-drum synth, exchange kick drum tails and tune them easily using semitones or you can completely exchange given source sounds.

Maven Enforcer has two goals: enforcer:enforce and enforcer:display-info. The enforce goal runs during a project build to execute rules specified in the configuration, while the display-info goal shows current information about the built-in rules that are present in the project’s pom.xml. Let’s define the enforce goal in the executions tag.