I'm using artifact plugin with sftp for deploying... ain't that secure enough?
I also must deploy wars, ejb, jars and sars... so having them all go trough artifact plugin helps a lot.
We need to use artifact plugin for deploying because we have not been able to make jar:deploy/deploy-snapshot to run without asking for a password and we need this process to be automated for use from cruisecontrol.
Any tip for doing this automation work?
I've already tried using rsa/dsa authentication putting public keys on the server, etc, etc... still no success. It keeps asking for a password.
I point maven to the keyfile with "-i /path/to/priv_key" in maven.ssh.args or something like that (also in scp args).
To note is that when a try this login in with plain ssh for shell access, the rsa/dsa auth works.
I'm using OpenSSH under linux, the repositories are a linux box with OpenSSH and a solaris box with whatever ssh implementation they have .
El vie, 07-05-2004 a las 04:18, Maczka Michal escribió:
> -Original Message-
> From: Pablo Lalloni [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 06, 2004 9:36 PM
> To: [EMAIL PROTECTED]
> Subject: jar & war plugins
>
>
> I just wanted to know if the jar plugin is going to be modified so it
> make deployments through the artifact plugin...
>
Not for Maven 1.0.
Atifact plugin (in fact it's more tag liblary then plugin) does not yet
support secure deployemnts to repositories over scp protocol
( artifact plugin requires that passwords are kept in open text in
properties files ).
After Maven 1.0 (probably Maven 1.1) there are plans to integrate Wagon with
Maven. Wagon is small liblary which will allow to deploy and fetch artifacts
from repositories using http, ssh, ftp and file protocols. Protocols
providers are pluggabe and more can be added but existing list probably
already covers most of the cases.
> See, I've done this modification for the project I'm working on but
> don't like the idea of having our own versions of maven plugins, so
> maybe I could send/submit/whatever the modifications to be
> incorporated
> in maven distribution.
>
> I've also modified the war plugin to support setting the ClassPath on
> the manifest file just like the ejb and ear plugin does.
>
You might check issues which are stored in maven's JIRA. This issue is
alredy there with some comments.
Michal
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
