Here's an example build.properties entry, using this.
maven.repo.list=t1 maven.repo.t1=scpexe://t1.somewhere.com maven.repo.t1.directory=/www/maven maven.repo.t1.username=myname maven.repo.t1.group=mygroup maven.repo.t1.ssh.executable=plink maven.repo.t1.ssh.args=-C maven.repo.t1.scp.executable=pscp maven.repo.t1.scp.args=-C
--Leif
At 06:45 PM 11/19/2003, you wrote:
Hi Leif,
(Sorry for CC'ing back to the list again, but they'll probably want to review this)
Sounds like a good idea - perhaps a new protocol could be added to artifact (scpexe:// ?) that uses the mentioned parameters. Alternatively, it might be a branch of the existing protocl based on another property - however, I think the new protocol idea is better.
Michal, do you have any current thoughts on the direction of artifact?
Your changes would be welcome - just submit a patch to JIRA when you are done and I'll commit it and release a new version. Let me know if you want to bounce any more ideas around.
Cheers, Brett
-----Original Message----- From: Leif Nelson [mailto:[EMAIL PROTECTED] Sent: Thursday, 20 November 2003 11:33 AM To: Brett Porter Subject: RE: deploy-snapshot vs. war:deploy-snapshot and ear:deploy-snapshot
OK. I looked in the cvs repository, and it seems that the artifact plugin hasn't been touched in a while... (2-3 months). If I fixed it up to work with maven.ssh.executable and maven.scp.executable, would that help? Or, is this already on someone's task list..
Thanks again,
--Leif
At 11:26 AM 11/20/2003 +1100, you wrote:
Your analysis is correct.
Artifact needs to be more friendly to SSH, jar:deploy should use artifact. The reason it hasn't moved is because of the fact that artifact still needs more work.
Cheers, Brett
> -----Original Message----- > From: Leif Nelson [mailto:[EMAIL PROTECTED] > Sent: Thursday, 20 November 2003 11:19 AM > To: [EMAIL PROTECTED] > Subject: jar:deploy-snapshot vs. war:deploy-snapshot and > ear:deploy-snapshot > > > Hi all- > > I'm confused about deployments with maven rc1. I have the > jar deployment > stuff working perfectly. Setting these properties: > > maven.repo.central=myrepo.mycompany > maven.repo.central.directory=/www/maven-repo > maven.username=lnelson > maven.remote.group=users > maven.ssh.executable=plink > maven.scp.executable=pscp > > Well, I tried to start using ear & war deployment. And, it didn't > work. After some research, I found that these plugins use > the "artifact" > plugin to do their deployments. So, I added all these properties to > support this: > > maven.repo.list=myrepo > maven.repo.myrepo=scp://myrepo.mycompany > maven.repo.myrepo.directory=/www/maven-repo > maven.repo.myrepo.username=lnelson > maven.repo.myrepo.privatekey=/private/private-key > maven.repo.myrepo.passphrase=mypassphrase # YUCKY! Want to > use pageant! > maven.repo.myrepo.group=users > > But, It seems that these plugins do the SAME thing, but the > artifact plugin > won't work with putty and pageant. It requires me to provide > my private > key and passphrase (and it can't read the putty private keys). > > So, am I missing something here? How do I deploy wars & > ears using putty > (pscp) and pageant? That's the most convenient! It looks like the > artifact plugin uses JCraft ( > http://www.jcraft.com/jsch/index.html ) which > doesn't > support the idea of ssh-agents. > > Thanks, > > --Leif > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > ________________________________________________ Leif Nelson [EMAIL PROTECTED] Lawrence Livermore National Laboratory (406) 863-9187 ICQ: 9389793 Yahoo: nelson9087 Fax: (406) 863-9030 AIM: nelson9087 Jabber: [EMAIL PROTECTED]
________________________________________________
Leif Nelson [EMAIL PROTECTED]
Lawrence Livermore National Laboratory (406) 863-9187
ICQ: 9389793 Yahoo: nelson9087 Fax: (406) 863-9030
AIM: nelson9087 Jabber: [EMAIL PROTECTED]
