Hi Oliver, The user guide definitely needs an update. Only SSH2 is supported in artifact (hence the reason the rsa1 key failed).
I don't know about your Auth fail - did -X help? I'm on holiday, so no chance to look at the group issue. It is already in JIRA - if you can provide more info or a patch, it would be welcomed. Cheers, Brett On Thu, 29 Jul 2004 16:38:46 +0200, Oliver Noelle <[EMAIL PROTECTED]> wrote: > Now that we are moving towards maven-1.0 I wanted to move to the new > deploy method via the artifact plugin. > > I had a hard time today, with the following issues: > > 1. where are the properties documented that you necessarily need for > deploying anything? Only in the artifact plugin itself? > > => I think there should be an introduction for setting up repositories > and the corresponding properties in the user guide > => the deprecated properties (eg. maven.repo.central) should be > documented as deprecated in the user guide > > 2. using Openssh on a linux server (the repository to deploy to) and > maven on a win2k box (from where I want to deploy) I cannot connect with > the scp protocol using these settings in my build.properties: > > # repositories for deploying > maven.repo.list=carit > > #settings for repository 'carit' > maven.repo.carit=scp://dude > maven.repo.carit.username=user.name > maven.repo.carit.directory=/exports/maven/repository > maven.repo.carit.group=developer > maven.repo.carit.privatekey=u:/.ssh/identity > maven.repo.carit.passphrase=user > maven.repo.carit.compress=true > > - using a key 'identity' generated with ssh-keygen with default > properites: > > Deploying to repository: carit > Using private key: u:\.ssh\identity > com.jcraft.jsch.JSchException: invaid privatekey: u:\.ssh\identity > Failed to deploy to: carit Reason: Cannot connect. Reason: invaid > privatekey: u:\.ssh\identity > > - using a key 'id_dsa' generated with ssh-keygen -t dsa > or using a key 'id_dsa' generated with ssh-keygen -t rsa > > Deploying to repository: carit > Using private key: u:\.ssh\id_dsa > com.jcraft.jsch.JSchException: Auth fail > at com.jcraft.jsch.Session.connect(Unknown Source) > [...] > at com.werken.forehead.Forehead.main(Forehead.java:581) > Failed to deploy to: carit Reason: Cannot connect. Reason: Auth fail > > => anything I am missing here to use the scp protocol? (I could get the > scpexe protocol working) => Any more documentation on this topic than > the few lines documented within the artifact plugin? > > 3. file permissions in the central repository > after I finally managed to use scpexe for deploying, I realised that the > file permissions of deployed files are not set correctly. As we are > working extensively with snapshots and more than one developer (and > nightly builds, too) possibly deploy the same artifact, this is pretty > much a blocker for us! > > => Any plans of when a bugfix or workaround for that might be available? > > Any help appreciated, > > Oliver > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
