Will do.  I'll download 2.0.2 when it becomes available and try again.  

Is there a good series of steps for ensuring my environment is "clean"?  I 
usually delete my repository and try not to specify any special extensions or 
mirrors unless I specifically need them for the test I'm running.  I'm just 
worried that this is user error because so many others are having success with 
your fix.

K.C.

-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 09, 2006 2:19 PM
To: Maven Users List
Subject: Re: call for testers: scp wagon


Hi KC,

At this point we will be releasing the code as is. Please let us know
if you continue to experience it after the 2.0.2 release, and we will
pursue this in greater depth again with the jsch developers.

- Brett

On 1/10/06, KC Baltz <[EMAIL PROTECTED]> wrote:
> No, I hadn't deleted anything before;  I misunderstood the original email.
>
> That said, I just deleted:
> wagon-ssh-1.0-alpha-5.jar
> wagon-provider-api-1.0-alpha-5.jar
> jsch-0.1.23.jar
>
> and tried it again with no luck.  I'm still getting "session is down" errors. 
>  Here is the directory listing for my M2_HOME/lib dir:
>
> C:\>dir \java\maven-2.0.1\lib
>  Volume in drive C has no label.
>  Volume Serial Number is 4C29-BBAD
>
>  Directory of C:\java\maven-2.0.1\lib
>
> 01/09/2006  08:31 AM    <DIR>          .
> 01/09/2006  08:31 AM    <DIR>          ..
> 12/11/2005  03:03 PM            30,117 commons-cli-1.0.jar
> 12/11/2005  08:27 PM             4,047 doxia-sink-api-1.0-alpha-6.jar
> 01/06/2006  10:59 AM           117,174 jsch-0.1.24.jar
> 12/11/2005  11:36 PM            78,377 maven-artifact-2.0.1.jar
> 12/11/2005  11:39 PM            49,156 maven-artifact-manager-2.0.1.jar
> 12/12/2005  01:42 AM           134,342 maven-core-2.0.1.jar
> 12/11/2005  11:53 PM             8,509 maven-error-diagnostics-2.0.1.jar
> 12/11/2005  11:30 PM            80,418 maven-model-2.0.1.jar
> 12/12/2005  12:00 AM             5,647 maven-monitor-2.0.1.jar
> 12/11/2005  11:57 PM             8,246 maven-plugin-api-2.0.1.jar
> 12/11/2005  11:59 PM            31,879 maven-plugin-descriptor-2.0.1.jar
> 12/11/2005  11:48 PM            16,202 
> maven-plugin-parameter-documenter-2.0.1.j
> ar
> 12/11/2005  11:54 PM            23,876 maven-plugin-registry-2.0.1.jar
> 12/11/2005  11:42 PM            30,166 maven-profile-2.0.1.jar
> 12/11/2005  11:44 PM           105,316 maven-project-2.0.1.jar
> 12/11/2005  11:50 PM             5,515 maven-reporting-api-2.0.1.jar
> 12/11/2005  11:34 PM            19,612 maven-repository-metadata-2.0.1.jar
> 12/11/2005  11:32 PM            43,713 maven-settings-2.0.1.jar
> 12/11/2005  03:04 PM            13,407 
> plexus-interactivity-api-1.0-alpha-4.jar
> 12/11/2005  03:03 PM             5,852 wagon-file-1.0-alpha-5.jar
> 12/11/2005  03:03 PM             7,661 wagon-http-lightweight-1.0-alpha-5.jar
> 01/06/2006  10:59 AM            42,584 
> wagon-provider-api-1.0-alpha-6-20060105.0
> 62346-7.jar
> 01/06/2006  10:58 AM            32,044 
> wagon-ssh-1.0-alpha-6-20060105.062346-2.j
> ar
>               23 File(s)        893,860 bytes
>                2 Dir(s)  58,364,706,816 bytes free
>
> -----Original Message-----
> From: Stephen Duncan [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 07, 2006 7:18 AM
> To: Maven Users List
> Subject: Re: call for testers: scp wagon
>
>
> When putting them into your 2.0.1 lib directory, did you delete the
> equivalent jars that were already there?
>
> -Stephen
>
> On 1/6/06, KC Baltz <[EMAIL PROTECTED]> wrote:
> > This is failing for me.  I am continuing to get the "session is down" 
> > exception.
> > I'm not sure what debugging information you'd like to see.  I'm getting the 
> > same basic stack trace I've always gotten with a root cause like this:
> >
> > Caused by: com.jcraft.jsch.JSchException: session is down
> >         at com.jcraft.jsch.Channel.connect(Unknown Source)
> >         at 
> > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:125)
> >         ... 22 more
> >
> > I tried downloading the jars you specified and putting them in my 2.0.1 lib 
> > directory.  I also tried downloading the 2.0.x release (without modifying 
> > its /lib directory) and that failed as well.
> >
> > My build is on Windows XP, the remote repository is Solaris 10.
> >
> > K.C.
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Brett Porter [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, January 04, 2006 11:34 PM
> > 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-20060105.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-20060105.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]
> >
> >
>
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>
> ---------------------------------------------------------------------
> 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]

Reply via email to