scpexe uses the external scp command you would have been using under RC2. This was intended to be deprecated for some time, and we switched the default to the Java based SSH implementation.
We'd be happy to help debug your issue with the new version: do you know why rm -f /home/maven/maven-deployer-64484.zip failed remotely? Does it still exist there, and do you have permissions to remove it? - Brett On Tue, 13 Jul 2004 14:13:39 -0500, Craig S. Cottingham <[EMAIL PROTECTED]> wrote: > I just upgraded to 1.0 final from 1.0-rc2. jar:deploy-snapshot used to > work; now it doesn't. However, I *can* get it to work. > > From project.properties: > > maven.repo.list=server1 > maven.repo.server1=scp://server1.(my_employer).com > maven.repo.server1.directory=/home/maven > maven.repo.server1.group=maven > maven.repo.server1.compress=true > > And from ~/build.properties: > > # user-specific properties for Maven > maven.repo.server1.username=ccotting > maven.repo.server1.privatekey=/home/ccotting/.ssh/id_dsa > > When I try to execute the jar:deploy-snapshot goal: > > $ maven -X jar:deploy-snapshot > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0 > > Initializing Plugins! > ... > jar:deploy-snapshot: > [echo] maven.repo.list is set - using artifact deploy mode > Will deploy to 1 repository(ies): server1 > Deploying to repository: server1 > host: 'server1.(my_employer).com' > Using private key: /home/ccotting/.ssh/id_dsa > Deploying: project.xml-->(my_employer)/poms/frameworx-SNAPSHOT.pom > deployNotCompressed=false > Executing command: scp -t /home/maven/maven-deployer-64484.zip > Executing command: unzip -uo /home/maven/maven-deployer-64484.zip -d > /home/maven > > SSH_MSG_DISCONNECT: 2 Received ieof for nonexistent channel 0. > Executing command: rm -f /home/maven/maven-deployer-64484.zip > > Failed to deploy to: server1 Reason: Cannot execute remote command: rm > -f /home/maven/maven-deployer-64484.zip > > org.apache.maven.deploy.exceptions.TransferFailedException: Cannot > execute remote command: rm -f /home/maven/maven-deployer-64484.zip > > BUILD FAILED > File...... > /home/ccotting/.maven/cache/maven-artifact-plugin-1.4/plugin.jelly > Element... artifact:artifact-deploy-snapshot > Line...... 156 > Column.... 13 > Unable to deploy to any repositories > com.werken.werkz.UnattainableGoalException: Unable to obtain goal > [jar:deploy-snapshot] -- > /home/ccotting/.maven/cache/maven-artifact-plugin-1.4/plugin.jelly:156: > 13: <artifact:artifact-deploy-snapshot> Unable to deploy to any > repositories > ... > > === SNIP === > > Now, remember that I said that I could get it to work? By changing the > protocol in project.properties to scpexe: > > maven.repo.server1=scpexe://server1.(my_employer).com > > jar:deploy-snapshot works fine. User head space, or genuine issue? > > -- > Craig S. Cottingham > [EMAIL PROTECTED] > OpenPGP key available from: > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7977F79C > > --------------------------------------------------------------------- > 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]
