scp fails when deploying to repository on Solaris 9 - session is down
---------------------------------------------------------------------

         Key: WAGONSSH-39
         URL: http://jira.codehaus.org/browse/WAGONSSH-39
     Project: wagon-ssh
        Type: Bug

    Versions: 1.0-alpha-6    
 Environment: Client:  Maven 2.0.2 running Windows XP Pro, JDK 1.5. 
Server:  SunOS hostname 5.9 Generic_112233-05 sun4u sparc SUNW,Sun-Fire-280R
    Reporter: K.C. Baltz


When I try to deploy my project to a local repository on a Solaris 9 machine, I 
get the "session is down" error that has happened before.  If I try to deploy 
to the same repository on Solaris 10, everything works great.  

Here's the failing output:

[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from ldap
: [WARNING] repository metadata for: 'snapshot 
com.copart.core:core:1.0-SNAPSHOT' could not be retrieved from repository: ldap 
due to an error: Error occured while downloading 
'com/copart/core/core/1.0-SNAPSHOT/maven-metadata.xml.sha1' from the remote 
repository:[ldap] -> scp://solaris9/export/home/kcbaltz/testM2Repo
[INFO] Repository 'ldap' will be blacklisted
: Uploading: scp://solaris9/export/home/kcbaltz/testM2Repo/com/copart/core/core
/1.0-SNAPSHOT/core-1.0-20060124.004001-5.jar
[INFO] 
----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] 
----------------------------------------------------------------------------
[INFO] Error deploying artifact: Error occured while deploying 
'com/copart/core/core/1.0-SNAPSHOT/core-1.0-20060124.004001-5.jar' to remote 
repository: scp://solaris9/export/home/kcbaltz/testM2Repo

session is down




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to