I know uploading through SCP is possible. At my previous workplace we uploaded the artifacts through SCP directly to the server location and not the web location. I have replicated it right down as I remember it. There could possible just be some user authentication problem. I could possibly solve this by adding the user build public key into its own authorized_keys file. Then maven should have no problem uploading via scp without submitting the password for the user.
*Trying the http URL for distribution management:* Uploading: http://maven-vm1:8080/nexus/content/repositories/releases/com/company/myApp/2.4.0/myApp-2.4.0.pom [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1:04.762s [INFO] Finished at: Mon Mar 25 09:25:44 CET 2013 [INFO] Final Memory: 31M/803M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project myApp: Failed to deploy artifacts: Could not transfer artifact com.company:myApp:jar:2.4.0 from/to releases (http://maven-vm1:8080/nexus/content/repositories/releases): Failed to transfer file: http://maven-vm1:8080/nexus/content/repositories/releases/com/company/myApp/2.4.0/myApp-2.4.0.jar. Return code is: 401, ReasonPhrase:Unauthorized. -> [Help 1] -- View this message in context: http://maven.40175.n5.nabble.com/maven-deploy-artifacts-to-Nexus-repository-tp5751512p5751781.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
