SSH key authentication isn’t supported yet, you can follow this issue.

One thing you can do is to use a “maven-properties-plugin” to read authentication data (user and password) from a file and define ${user} and ${pass} properties which can then be used to configure the copy plugin scp copy operation.

“maven-properties-plugin” has a “verbose” flag just for that purpose – setting it to “false” doesn’t echo the properties defined. I use it to set FTP/SCP paths for my tests this way.

Currently I have tied the scp to a package phase, but this obviously is not a solution.

alpha-deploy

com.goldin.plugins
maven-copy-plugin
0.2.3.6

deploy-war
package

copy

scp://username:password@alpha.company.com:war
${project.build.directory}/myweb.war

Can you give me an example of how to copy the war to a remote server? Also, a solution which uses username and password from my settings file or even better – authenticate via my ssh generated key.

Thanks for any input.

Tying scp plugin execution to a certain phase is what I did, I think it was “deploy”. You can try executing the plugin from the command line but I never did so. What is the reason you don’t want to bind it to existing phase?

great plugins you have written!

I am trying to use the upload scp functionality from the maven-copy-plugin. I want to copy a generated war to a remote jetty server.

Is it possible to execute the copy command on demand with some mvn command or one have to use the executions maven feature? I do not want to tie uploading my war to remote server to be redeployed in the jetty container to some existing maven phase.

Thanks for the answer!