Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Number of attachments :
Description
I have implemented an ScpExeDeployer plugin (like I said I would back in November!). When I upgraded to RC4, I saw that you were "serious" about getting rid of the old scp/ssh type of deployment.
Anyways, I really need to have the ssh-agent type of support in the deployment artifacts, so I implemented this plugin. It's backwards compatible with folks that supply the old maven.ssh.executable, maven.ssh.args, maven.scp.executable, maven.scp.args. I also made it look for these params in "server-specific" props like you do with the new stuff.. maven.repo.x.ssh.executable, maven.repo.x.ssh.args, maven.repo.x.scp.executable, maven.repo.x.scp.args. So, if someone wanted to deploy with different args, or different commands to different servers, the plugin would support that.
This work was done in regards to this email thread.. http://nagoya.apache.org/eyebrowse/ReadMsg?listName=users@maven.apache.org&msgNo=8065
Thanks much for consideration. ![]()
--Leif
Here's the patch.