I have setup a job that executes "mvn install" periodically. I have decided to let Hudson handle my artifact deployment after a full successful build by choosing option "Deploy artifacts to Maven repository" under Post-Build Actions. My method of deployment is FTP since my remote Maven repo only allows FTP clients. When I execute a build the build succeeds but deployment fails. Hudson stacktrace reports "Unsupported Protocol: ftp".

I found this information on Apache Maven FAQ that helped me resolve it. I initially thought Hudson was going to execute all Maven actions through my Maven installation but it appears for this setting it executes its own Maven env which after checking did not bundle FTP or SSH support. SCP was supported out of the box.

FAQ: http://maven.apache.org/plugins/maven-deploy-plugin/faq.html

Checking under this direcotry I did not see any Maven FTP or SSH support. I followed the Apache Maven FAQ instructions and dropped "wagon-ftp-1.0-beta-2.jar" and "commons-net-ftp-2.0.jar" here and restarted Hudson. After this step I was able to successfully push artifacts into my remote repository.

<HUDSON_ENV_FOR_MY_BUILDS>/plugins/maven-plugin/WEB-INF/lib

Solution:
Bundle the necessary Maven plugins to support all transport protocols for artifact deployment that Maven currently supports via the Wagon plugin:
http://maven.apache.org/wagon/

At a minimum the Help documentation should say what is supported since it was not clear at all what transports were supported until I executed each one.

Thanks