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 on.
Assuming your server understands scp, you might put in your pom something like:
<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh</artifactId>
<version>1.0</version>
</extension>
</extensions>
</build>
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 this.
Regards,
Russ
On Oct 12, 2013, at 4:29 PM, Kevin Krumwiede <[email protected]> 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://chalcodes.com/maven
>
> 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: [email protected]
> For additional commands, e-mail: [email protected]
>
-----------------
Author, Getting Started with Apache Maven
<http://www.packtpub.com/getting-started-with-apache-maven/video>
Come read my webnovel, Take a Lemon <http://www.takealemon.com>,
and listen to the Misfile radio play <http://www.fuzzyfacetheater.com/misfile/>!
