I'm trying to update the docs for this change, but I'm not sure I understand how wagon works. The patch did not add any new dependencies to the plugin. However, isn't the wagon-ssh-external provider need to use scpexe? Or should that be provided by the project using the plugin?
Regarding what protocols the plugin now supports, am I reading the wagon source correctly if I say the this plugin now supports the following protocols for the target repo?
and also this one, which also extends CommandExecutor
I discovered this in trying to move a staged release today.
The attached patch fixes it for me (I used scpexe:// for the target repo, which fails without the patch and succeeds with the patch). The earlier cast to ScpWagon for the lines in question seems overly restrictive and exclusionary.