Maven deploy Plugin: Difference between revisions
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
=Running as Part of a Lifecycle= | =Running as Part of a Lifecycle= | ||
See: | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[Maven_install_Plugin#Deploying_Programmatically_an_Artifact_under_a_Different_Name_than_its_artifactId|install plugin - Deploying Programmatically an Artifact under a Different Name than its artifactId]] | |||
</blockquote> | |||
=Examples= | =Examples= | ||
Revision as of 17:31, 18 November 2016
External
Internal
Overview
The deploy plugin copies artifacts into a remote repository (the install plugin copies artifacts into the local repository).
Running as Part of a Lifecycle
See:
Examples
Install Arbitrary Files as Binaries and Sources
mvn deploy:deploy-file -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B \
-Dpackaging=jar -Dfile="C:\tmp\jta-1.0.1B.jar" \
-Durl="file://C:\Documents and Settings\user1\.m2" -DrepositoryId=repository
mvn deploy:deploy-file -DgroupId=ec.template -DartifactId=test -Dversion=1 -Dpackaging=zip \ -Dfile=./test.zip -Durl=https://username:mypasswd@example.com/nexus/content/repositories/libs-release-local/blah
This will create (with appropriate permissions) https://example.com/nexus/content/repositories/libs-release-local/blah/ec/template/test/1/test-1.zip
Deploying Programmatically an Artifact under a Different Name than its artifactId
See: