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 <[email protected]> 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 <[email protected]> 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 <[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] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
