Difference between revisions of "Deploying Single Files with Maven"
(Add commands to install/deploy files with Maven even if they’re not under Maven control.) |
(Turns out, you actually want packaging to be “jar” so that it actually keeps the JAR file after uploading.) |
||
| Line 1: | Line 1: | ||
In order to deploy single files that are not controlled by Maven, you need the <tt>deploy:deploy-file</tt> goal. | In order to deploy single files that are not controlled by Maven, you need the <tt>deploy:deploy-file</tt> goal. | ||
| − | # mvn deploy:deploy-file -Dfile=''file'' -DgroupId=''groupId'' -DartifactId=''artifactId'' -Dpackaging= | + | # mvn deploy:deploy-file -Dfile=''file'' -DgroupId=''groupId'' -DartifactId=''artifactId'' -Dpackaging=jar -Dversion=''version'' -DrepositoryId=''repositoryId'' -Durl=scp://''host''/''path'' |
The repository ID is necessary in case you have authentication information defined for your repository. | The repository ID is necessary in case you have authentication information defined for your repository. | ||
Revision as of 10:55, 3 August 2012
In order to deploy single files that are not controlled by Maven, you need the deploy:deploy-file goal.
# mvn deploy:deploy-file -Dfile=file -DgroupId=groupId -DartifactId=artifactId -Dpackaging=jar -Dversion=version -DrepositoryId=repositoryId -Durl=scp://host/path
The repository ID is necessary in case you have authentication information defined for your repository.
To install a file only locally, use:
# mvn install:install-file -Dfile=file -DgroupId=groupId -DartifactId=artifactId -Dpackaging=pom -Dversion=version
