You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Delany <de...@gmail.com> on 2025/10/20 13:55:45 UTC
Wagon SSH not working
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,
Re: Wagon SSH not working
Posted by Nils Breunese <ni...@breun.nl>.
Delany <de...@gmail.com> wrote:
> I'm curious about companies that don't use an HTTP server / paid product to
> manage their artifacts.
I’m sorry to hear you’re struggling with this. Where I work we do use a commercial solution, and it isn’t Nexus, so I can’t help you with this, but maybe someone else can.
Nils.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Wagon SSH not working
Posted by Delany <de...@gmail.com>.
Hi Nils,
We have been using Nexus for years. Recently we've had a lot of trouble
with:
- their borked migration off OrientDB. After going deep trying to make it
work we just had to set everything up from scratch
- we've been unable to come up with an effective backup procedure (I think
this was because cleanup policies fail to reduce disk space)
- when LastPass browser extension is used with the WebUI (Ext JS) a
dangerous interaction occurs that leads to permissions of one user being
applied to another
- the issue tracker https://github.com/sonatype/nexus-public/issues is not
the real issue tracker. Its just a cacophony of desperate people messaging
into the void. Unless you're a paying customer Sonatype doesn't want to
hear from you
We're just tired of the mediocrity. And now that the community edition is
enforcing usage limits we are constrained in what/how often we can build.
The only use of Nexus I can't see us avoiding is the proxy for Maven
Central. Maybe squid / trafficserver could do this but presumably not with
the same level of convenience.
I'm curious about companies that don't use an HTTP server / paid product to
manage their artifacts.
Regards,
Delany
On Wed, 5 Nov 2025 at 16:18, Nils Breunese <ni...@breun.nl> wrote:
> Hi Delany,
>
> In the corporate environments I’ve worked in artifacts are generally built
> using a CI tool (GitLab CI or GitHub Actions, for instance) that runs Maven
> (via Maven Wrapper) as part of CI pipeline and then deploys the artifacts
> to a private Maven repository hosted using something like Artifactory or
> Nexus. Or you could deploy to a public repository like Maven Central or one
> you host yourself if you intend to make the artifacts available to the
> public. When the result of a build is an application that you want to run
> in a container environment, the result of a pipeline could also be a
> container image getting pushed to a container registry instead of JAR/WAR
> archives getting pushed to a Maven repository. Or you could do both.
>
> But there are lots of ways to use Maven, it’s best to start with your
> needs and look for solutions from there.
>
> Nils.
>
> > Op 5 nov 2025, om 14:43 heeft Delany <de...@gmail.com> het
> volgende geschreven:
> >
> > Hi Tamas.
> >
> > Thanks, its working now with scpexe://...
> > I would not have figured that out by myself!
> >
> > The reason I want to use ssh for deploy is that using NFS pushes the
> > security boundary out to the network perimeter.
> > I'm just surprised/horrified this isn't more widely used. Or maybe people
> > do? I wish I knew more about how others actually use Maven.
> >
> > Regards,
> >
> > On Mon, 20 Oct 2025 at 16:24, Tamás Cservenák <ta...@cservenak.net>
> wrote:
> >
> >> 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 <de...@gmail.com>
> 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: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Wagon SSH not working
Posted by Nils Breunese <ni...@breun.nl>.
Hi Delany,
In the corporate environments I’ve worked in artifacts are generally built using a CI tool (GitLab CI or GitHub Actions, for instance) that runs Maven (via Maven Wrapper) as part of CI pipeline and then deploys the artifacts to a private Maven repository hosted using something like Artifactory or Nexus. Or you could deploy to a public repository like Maven Central or one you host yourself if you intend to make the artifacts available to the public. When the result of a build is an application that you want to run in a container environment, the result of a pipeline could also be a container image getting pushed to a container registry instead of JAR/WAR archives getting pushed to a Maven repository. Or you could do both.
But there are lots of ways to use Maven, it’s best to start with your needs and look for solutions from there.
Nils.
> Op 5 nov 2025, om 14:43 heeft Delany <de...@gmail.com> het volgende geschreven:
>
> Hi Tamas.
>
> Thanks, its working now with scpexe://...
> I would not have figured that out by myself!
>
> The reason I want to use ssh for deploy is that using NFS pushes the
> security boundary out to the network perimeter.
> I'm just surprised/horrified this isn't more widely used. Or maybe people
> do? I wish I knew more about how others actually use Maven.
>
> Regards,
>
> On Mon, 20 Oct 2025 at 16:24, Tamás Cservenák <ta...@cservenak.net> wrote:
>
>> 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 <de...@gmail.com> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Wagon SSH not working
Posted by Bernd Eckenfels <ec...@zusammenkunft.net>.
Hello Thorsten,
Thorsten Heit schrieb am 05.11.2025 19:42
> Have you tried to use https://github.com/mwiede/jsch instead of the old
> one from jcraft? It uses more modern crypto algorithms and can be used
> as a drop-in replacement.
Oh yes, I think we actually did in the past and it worked, I totally forgot
about it.
I think you need to specify it as a dependency of the extension (or the plugin),
and it is picked up,
Gruß
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Wagon SSH not working
Posted by Thorsten Heit <th...@gmx.de.INVALID>.
Hi,
> we have been using wagon-ssh (extension) in our CIs, mostly for staging
> reports and test logs. We registered the ssh extension which is using
> JSch. However since we upgraded our SSH daemons with more modern cipher
> suites, that does not work anymore,
Just out of curiosity:
Have you tried to use https://github.com/mwiede/jsch instead of the old
one from jcraft? It uses more modern crypto algorithms and can be used
as a drop-in replacement.
Regards
Thorsten
Re: Wagon SSH not working
Posted by Bernd Eckenfels <ec...@zusammenkunft.net>.
Hello,
we have been using wagon-ssh (extension) in our CIs, mostly for staging
reports and test logs. We registered the ssh extension which is using
JSch. However since we upgraded our SSH daemons with more modern cipher
suites, that does not work anymore, We switched to a command execution
plugin using the native ssh command line (which also speeds up the
transfers), but it seems like sftpexe: (Wagon SSH External) would have
been a good alternative for us.
Gruß Bernd
> Delany schrieb am 05.11.2025 14:43 (GMT +01:00):
>> Hi Tamas.
>>
>> Thanks, its working now with scpexe://...
>> I would not have figured that out by myself!
>>
>> The reason I want to use ssh for deploy is that using NFS pushes the
>> security boundary out to the network perimeter.
>> I'm just surprised/horrified this isn't more widely used. Or maybe people
>> do? I wish I knew more about how others actually use Maven.
>>
>> Regards,
>>
>> On Mon, 20 Oct 2025 at 16:24, Tamás Cservenák <ta...@cservenak.net>
>> wrote:
>>
>> > 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 <de...@gmail.com>
>> 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: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Wagon SSH not working
Posted by Delany <de...@gmail.com>.
Hi Tamas.
Thanks, its working now with scpexe://...
I would not have figured that out by myself!
The reason I want to use ssh for deploy is that using NFS pushes the
security boundary out to the network perimeter.
I'm just surprised/horrified this isn't more widely used. Or maybe people
do? I wish I knew more about how others actually use Maven.
Regards,
On Mon, 20 Oct 2025 at 16:24, Tamás Cservenák <ta...@cservenak.net> wrote:
> 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 <de...@gmail.com> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Wagon SSH not working
Posted by Tamás Cservenák <ta...@cservenak.net>.
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 <de...@gmail.com> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org