scp is used, unless you configure putty. - Brett
On 1/6/06, dan tran <[EMAIL PROTECTED]> wrote: > I have both putty.exe and cygwin scpexe in my path. Putty if first. > > But i think maven picks up scp.exe, no sure thou > > -Dan > > > On 1/5/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > Ok, looking into it. Do you use putty? > > > > On 1/6/06, dan tran <[EMAIL PROTECTED]> wrote: > > > I actually did wipe out the snapshots of native-maven-plugin at beaver > > and > > > deploy the plugin again. Same problem at the end, but all the files > > seem > > > the be there. Strange! > > > > > > Thanks again. > > > > > > -Dan > > > > > > > > > > > > On 1/5/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi dan, > > > > > > > > I think this is almost certianly permissions problems with deploying > > > > that project, rather than an scpexe error, and though the returned > > > > error is limited, its all it gets back from the server :) > > > > > > > > I'll try to reproduce it, though. > > > > > > > > - Brett > > > > > > > > On 1/6/06, dan tran <[EMAIL PROTECTED]> wrote: > > > > > it is a great joice to see scp working with all the correct > > persmission > > > > > settings > > > > > there is one minor problem with scpexe thou > > > > > > > > > > Tested with the recommended snapshot build using scp, sftp,and > > scpexe. > > > > > > > > > > The project ( maven-native) consists of 2 parents, 6 jars, and 1 > > plugin > > > > > projects. > > > > > the plugin deploy always fails at the last step for SCPEXE. I also > > fails > > > > > when I > > > > > deploy the plugin alone. > > > > > > > > > > > > > > > [INFO] [deploy:deploy] > > > > > [INFO] Retrieving previous build number from snapshots > > > > > Uploading: > > > > > > > scpexe://repo1.maven.org/home/projects/maven/repository-staging/snaps > > > > > > > > > > > hots/maven2/org/codehaus/mojo/native-maven-plugin/1.0-alpha-1-SNAPSHOT/native-ma > > > > > ven-plugin-1.0-alpha-1-20060105.181308-10.jar > > > > > [INFO] Retrieving previous metadata from snapshots > > > > > [INFO] Uploading repository metadata for: 'artifact > > > > > org.codehaus.mojo:native-mav > > > > > en-plugin' > > > > > [INFO] Retrieving previous metadata from snapshots > > > > > [INFO] Uploading repository metadata for: 'snapshot > > > > > org.codehaus.mojo:native-mav > > > > > en-plugin:1.0-alpha-1-SNAPSHOT' > > > > > [INFO] Retrieving previous metadata from snapshots > > > > > [INFO] Uploading project information for native-maven-plugin > > > > > 1.0-alpha-1-2006010 > > > > > 5.181308-10 > > > > > [INFO] Retrieving previous metadata from snapshots > > > > > [INFO] Uploading repository metadata for: 'org.codehaus.mojo' > > > > > [INFO] > > > > > > > > > > > ------------------------------------------------------------------------- > > > > > --- > > > > > [ERROR] BUILD ERROR > > > > > [INFO] > > > > > > > > > > > ------------------------------------------------------------------------- > > > > > --- > > > > > [INFO] Error installing artifact's metadata: Error while deploying > > > > metadata: > > > > > Err > > > > > or executing command for transfer > > > > > > > > > > Exit code 1 - > > > > > > > > > > overall, it is a joice to see scp working with all the correct > > > > persmission > > > > > settings > > > > > > > > > > > > > > > > > > > > > > > > > On 1/5/06, Mike Perham <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > Brett, I switched from sftp to scp and it appears to work! I hope > > all > > > > > > of this can be released with 2.0.2 as we are planning a > > company-wide > > > > > > migration from 2.0 to 2.0.2 once it has been released and I have > > > > tested > > > > > > it internally. > > > > > > > > > > > > Is there any practical difference between the two transports? Why > > > > > > should I pick one versus the other? > > > > > > > > > > > > mike > > > > > > > > > > > > -----Original Message----- > > > > > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > > > > > Sent: Thursday, January 05, 2006 1:34 AM > > > > > > To: Maven Users List > > > > > > Subject: call for testers: scp wagon > > > > > > > > > > > > Hi, > > > > > > > > > > > > In the lead up to the 2.0.2 release, I'd like anyone experiencing: > > > > > > [WAGONSSH-28] session is down > > > > > > [WAGONSSH-30] hangs during deployment > > > > > > > > > > > > to test the following wagon snapshots: > > > > > > > > > > > > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon- > > > > > > ssh/1.0-alpha-6-SNAPSHOT/wagon- > > ssh-1.0-alpha-6-20060105.062346-2.jar > > > > > > by including it in your $M2_HOME/lib directory. > > > > > > > > > > > > Please also include: > > > > > > > > > > > > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon- > > > > > > provider-api/1.0-alpha-6-SNAPSHOT/wagon- > > > > provider-api-1.0-alpha-6-2006010 > > > > > > 5.062346-7.jar > > > > > > and > > > > > > > > http://www.ibiblio.org/maven2/com/jcraft/jsch/0.1.24/jsch-0.1.24.jar > > > > > > > > > > > > Replace any existing wagon/jsch libraries. > > > > > > > > > > > > Another way to test is to pick up the following integration build > > > > > > instead: > > > > > > > > > > > > http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-2006 > > > > > > 0105.071501.tar.gz > > > > > > > > > > > > With this build, you can also test scpexe and sftp if you were > > having > > > > > > any problems with them. > > > > > > > > > > > > Thanks! > > > > > > - Brett > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > 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] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > 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] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
