maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Russell Gold <>
Subject Re: Deploying third-pary jar via scp
Date Sun, 13 Oct 2013 13:36:23 GMT
Hi Kevin,

Yes, you will need a POM unless your server understands the http PUT command. When you issue
the mvn command, maven will look in your current directory for a POM even though it won't
be using any of its standard life cycles. Those will define any plugins, connectors, and so

Assuming your server understands scp, you might put in your pom something like:


Of course, you would still need a way to specify your credentials, preferably in your ~/.m2/settings.xml

There is a free version of the Nexus repository manager. That will be much easier to use than


On Oct 12, 2013, at 4:29 PM, Kevin Krumwiede <> wrote:

> I think I've solved my earlier question about my poms.  Now I need to
> deploy a third-party jar to my remote repo.  I tried this command:
> $ mvn deploy:deploy-file -DgroupId=de.kuxfamily -DartifactId=glasslib
> -Dversion=1.0 -Dpackaging=jar -Dfile=glasslib.jar
> -DrepositoryId=chalcodes -Durl=scpexe://
> It says there is no connector available.  I installed some jars in my
> ~/.m2/lib: wagon-ssh-2.5.jar, wagon-ssh-common-2.5.jar, and
> wagon-ssh-external-2.5.jar.  I also tried changing the protocol to
> scp.  No dice.
> Should I write a pom to deploy this artifact?  Can I deploy it as part
> of an existing project, and have it be available at compile time?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Author, Getting Started with Apache Maven <>

Come read my webnovel, Take a Lemon <>, 
and listen to the Misfile radio play <>!

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message