From: <Ste...@em...> - 2004-12-06 16:05:10
|
Hi, Thanks for your help. I have updated the doc in the web site, but there i= s some=20 problems with ssh. I am using Putty in Windows and i get the following error when i tried to= =20 release the plugin with plugin:repository-deploy : <snip> plugin:repository-deploy: [echo] maven.repo.list is set - using artifact deploy mode Will deploy to 1 repository(ies): maven-plugins-sf Deploying to repository: maven-plugins-sf Using private key: d:\temp\privKey com.jcraft.jsch.JSchException: invaid privatekey: d:\temp\privKey Failed to deploy to: maven-plugins-sf Reason: Cannot connect. Reason: inv= aid=20 privatekey: d:\temp\privKey BUILD FAILED File...... C:\Documents and=20 Settings\sbouchet\.maven\cache\maven-artifact-plugin-1.4.1\plugin.jelly Element... artifact:artifact-deploy Line...... 94 Column.... 13 Unable to deploy to any repositories Total time: 8 seconds Finished at: Mon Dec 06 16:55:56 CET 2004 And when i tried to use site:deploy, i get this error : BUILD FAILED File...... C:\Documents and=20 Settings\sbouchet\.maven\cache\maven-site-plugin-1.5.2\plugin.jelly Element... maven:user-check Line...... 121 Column.... 49 +------------------------------------------------------------------ | ERROR! | | You must specify a maven username in order to deploy the site! | You can either set this property in your ~/build.properties | or specify one on the command line: | | maven -Dmaven.username=3D${user.name}=20 [goal]+------------------------------------------------------------------ Total time: 1 minutes 29 seconds Finished at: Mon Dec 06 16:58:36 CET 2004 So i am a bit confused. I modified my project.properties file under maven-plugins dir like that : maven.repo.maven-plugins-sf.username=3Dle_phan maven.repo.maven-plugins-sf.privatekey=3Dd:/temp/privKey Regards, St=E9phane mav...@li... a =E9crit : after modifying the last two properties in http://cvs.sourceforge.net/viewcvs.py/maven-plugins/maven-plugins/project= .properties?rev=3D1.10&view=3Dmarkup You should be able to use plugin:repository-deploy to release the plugin You should already be able to use site:deploy to release the site if you have ssh setup correctly. Cheers, Brett On Fri, 3 Dec 2004 15:15:24 +0000, Andy Jefferson <an...@aj...> wrote= : >> Stephane, >> > >>> > WSo i am trying to release a new version of the kodo plugin, but i= don't >>> > know how ! > >> >> You need to create the plugin jar (see below). You then need to "scp"= it >> across to the website ... there's a maven directory on there. There's= a doc >> somewhere that defines this ... probably in the archives of this list. >> > >>> > I already made some changes to the CVS repo, but how to generate t= he new >>> > site's docs? and the plugin's jar ? > >> >> maven clean plugin >> will create the plugin >> >> maven site (from the kodo directory) >> will create its docs. You then need to copy those across to SourceFor= ge area. >> The details of how to do that are on SourceForge somewhere. Can't rem= ember >> the exact location. You need to scp the docs across to >> /home/groups/m/ma/maven-plugins/htdocs/kodo >> and then ssh to sourceforge and cd to the same location and unzip the= m. Then >> you need to do a "chmod 664 *" on the files you've added so others ca= n change >> them. Something like that anyway :-) >> > >>> > I made a mistake too, sorry, in the CVS tree : >>> > I make a kodo directory (empty) in parent directory, and i don't k= now how >>> > to remove it.... > >> >> It's CVS so you can add things but you can't just delete things ;-) >> For future reference, to do it on SourceForge you go to http://www.sf= .net and >> at the bottom is a link "Site Support" and you select that. You can t= hen >> submit a support request. I've just submitted one to remove that dire= ctory. >> >> -- >> Andy |
From: <Ste...@em...> - 2004-12-07 14:00:39
|
Hi, Well my SSH private key is now ok, i could run ssh on the command line as= explained. But when i tried to do a maven plugin:repository-deploy, i got an error : Failed to deploy to: maven-plugins-sf Reason: Cannot connect. Reason:=20 Session.connect: java.net.UnknownHostException: shell.maven-plugins.sf.ne= t BUILD FAILED File...... C:\Documents and=20 Settings\sbouchet\.maven\cache\maven-artifact-plugin-1.4.1\plugin.jelly Element... artifact:artifact-deploy Line...... 94 Column.... 13 Unable to deploy to any repositories Total time: 4 seconds Finished at: Tue Dec 07 14:52:03 CET 2004 If I change the host to maven-plugins.sf.net, i got this error : Failed to deploy to: maven-plugins-sf Reason: Cannot connect. Reason: Aut= h fail BUILD FAILED File...... C:\Documents and=20 Settings\sbouchet\.maven\cache\maven-artifact-plugin-1.4.1\plugin.jelly Element... artifact:artifact-deploy Line...... 94 Column.... 13 Unable to deploy to any repositories Total time: 15 seconds Finished at: Tue Dec 07 14:55:17 CET 2004 Thanks again for your help, St=E9phane Brett Porter a =E9crit : >>So i am a bit confused. >=20 >=20 > maven jar:deploy and site:deploy actually use different mechanisms: > the first is a Java SSH library, the latter justa command line ssh. >=20 >=20 >>I modified my project.properties file under maven-plugins dir like that= : >>maven.repo.maven-plugins-sf.username=3Dle_phan >>maven.repo.maven-plugins-sf.privatekey=3Dd:/temp/privKey >=20 >=20 > is this an Open SSH private key? It should work. >=20 > For site:deploy, you'll need to be able to run: > ssh le...@ma... > on the command line and have it work without a password >=20 > (you can use plink if you need to by setting maven.ssh.executable). >=20 > HTH, > Brett >=20 |
From: Brett P. <bre...@gm...> - 2004-12-07 22:23:54
|
I think I use shell1.maven-plugins.sf.net... isn't that specified in ${basedir}/project.properties as maven.repo.maven-plugins-sf? Cheers, Brett On Tue, 07 Dec 2004 14:59:14 +0100, st=E9phane bouchet <ste...@em...> wrote: > Hi, >=20 > Well my SSH private key is now ok, i could run ssh on the command line as= explained. >=20 > But when i tried to do a maven plugin:repository-deploy, i got an error : > Failed to deploy to: maven-plugins-sf Reason: Cannot connect. Reason:=20 > Session.connect: java.net.UnknownHostException: shell.maven-plugins.sf.ne= t >=20 > BUILD FAILED > File...... C:\Documents and > Settings\sbouchet\.maven\cache\maven-artifact-plugin-1.4.1\plugin.jelly > Element... artifact:artifact-deploy > Line...... 94 > Column.... 13 > Unable to deploy to any repositories > Total time: 4 seconds > Finished at: Tue Dec 07 14:52:03 CET 2004 >=20 > If I change the host to maven-plugins.sf.net, i got this error : > Failed to deploy to: maven-plugins-sf Reason: Cannot connect. Reason: Aut= h fail >=20 > BUILD FAILED > File...... C:\Documents and > Settings\sbouchet\.maven\cache\maven-artifact-plugin-1.4.1\plugin.jelly > Element... artifact:artifact-deploy > Line...... 94 > Column.... 13 > Unable to deploy to any repositories > Total time: 15 seconds > Finished at: Tue Dec 07 14:55:17 CET 2004 >=20 > Thanks again for your help, >=20 > St=E9phane >=20 > Brett Porter a =E9crit : >=20 >=20 > >>So i am a bit confused. > > > > > > maven jar:deploy and site:deploy actually use different mechanisms: > > the first is a Java SSH library, the latter justa command line ssh. > > > > > >>I modified my project.properties file under maven-plugins dir like that= : > >>maven.repo.maven-plugins-sf.username=3Dle_phan > >>maven.repo.maven-plugins-sf.privatekey=3Dd:/temp/privKey > > > > > > is this an Open SSH private key? It should work. > > > > For site:deploy, you'll need to be able to run: > > ssh le...@ma... > > on the command line and have it work without a password > > > > (you can use plink if you need to by setting maven.ssh.executable). > > > > HTH, > > Brett > > >=20 > |