Howdy,

First, I cannot reproduce your error, I get consistently:
"[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:3.1.2:deploy
(default-deploy) on project ssh: Failed to deploy artifacts/metadata:
Cannot access sftp://localhost/server with type default using the
available connector factories: BasicRepositoryConnectorFactory: Cannot
access sftp://localhost/server using the registered transporter
factories: HttpTransporterFactory, FileTransporterFactory,
WagonTransporterFactory -> [Help 1]"
(3.9.11 + Java 21) Please create a git repo with a reproducer.

Second, as I see wagon-ssh-external still uses javadoc tags (yikes),
and uses hint "scpexe":
https://github.com/apache/maven-wagon/blob/master/wagon-providers/wagon-ssh-external/src/main/java/org/apache/maven/wagon/providers/ssh/external/ScpExternalWagon.java#L57

So the protocol should be "scpexe" and not "sftp"?

Thanks
T

On Mon, Oct 20, 2025 at 3:56 PM Delany <[email protected]> wrote:
>
> Hi,
>
> Does anyone successfully use the Wagon SSH extension to deploy?
>
> I'm unable to get the wagon-ssh-external to work with Maven 3.
>
> It seems the ssh wagon is not registering the extension from the
> ./.mvn/extensions.xml file:
>
>   <extension>
>     <groupId>org.apache.maven.wagon</groupId>
>     <artifactId>wagon-ssh-external</artifactId>
>     <version>3.5.3</version>
>   </extension>
>
> Failed to deploy artifacts/metadata: Cannot access
> sftp://10.1.1.221/repo/snapshots with type default
> using the available connector factories:
> BasicRepositoryConnectorFactory: Cannot access
> sftp://10.1.1.221/repo/snapshots
> using the registered transporter factories: HttpTransporterFactory,
> HttpTransporterFactory, FileTransporterFactory,
> FileTransporterFactory, WagonTransporterFactory -> [Help 1]
>
> Why are there only 5 and why are there are only 3 unique?
>
> Apache Maven 3.9.11
>
> Thanks,

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to