[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Broken https: support in RC3 (at least under Debian)

From: Denny Valliant <valliant_at_unm.edu>
Date: 2006-01-24 22:26:16 CET

SEE THREAD BELOW:

Hi,

Taking the javasvn.jar from 0.9.102 and using it with 0.9.105 fixes the
problem.

I have now tested the command line version of JavaSVN and it is JavaSVN
1.0.2 that causes the problem.

I'll go and bother them now.

Regards,

Tony

>>-----Original Message-----
>>From: Mark Phippard [mailto:markp@softlanding.com]
>>Sent: 24 January 2006 16:02
>>To: users@subclipse.tigris.org
>>Subject: Re: [Subclipse-users] Repository connection broken
>>
>>"May Anthony-CTM001" <Tony.May@motorola.com> wrote on
>>01/24/2006 10:43:14
>>AM:
>>
>
>
>>>> I tried to update from version 0.9.37 to version 0.9.105.
>>>>
>>>> In doing so the connection to my SVN repository was broken. I had
>>>> problems last December when initially setting up the
>>
>>
>>connection to the
>
>
>>>> repository as it needs to go via a proxy. Fortunately the
>>
>>
>>JavaSVN team
>
>
>>>> had just fixed the problem (later released as JavaSVN
>>
>>
>>1.0.1), and when
>
>
>>>> I dropped the fixed version of javasvn.jar into the subclipse lib
>>>> folder, everything worked OK.
>>>>
>>>> The new problem is different and I get the following error:
>>>>
>>>> svn: {0} request failed on '<proxy url>'
>>>> svn: CONNECT of '<SVN repository site URL>:443': HTTP/1.0 407 Proxy
>>>> Authentication Required ('<SVN repository site URL>')
>>>>
>>>> On the archive I found older versions of the update site and have
>>>> discovered that subclipse version 0.9.102 does not have the new
>>>> problem (as well as fixing the original JavaSVN problem).
>>>>
>>>> Any ideas as to what the problem is?
>>>>
>>>> If someone can point me to update site for versions 0.9.103 and
>>>> 0.9.104 I could test those.
>>
>>
>>
>>You should provide as many details as possible so that JavaSVN
>>can attempt to address the problem.
>>
>>You could also likely get away with taking the javasvn.jar
>
>
>from 0.9.102 and using it with 0.9.105.

>>
>>Mark
>>
>>
>>
>>_______________________________________________________________
>>______________
>>Scanned for SoftLanding Systems, Inc. and SoftLanding Europe
>>Plc by IBM Email Security Management Services powered by MessageLabs.
>>_______________________________________________________________
>>______________
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
>>For additional commands, e-mail: users-help@subclipse.tigris.org
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org

Sebastian Bauer wrote:

> Hello,
>
> using the RC3 of subclipse, I'm unable to do anything useful with
> subclipse, at least not using the https: address scheme. I.e. I
> neighter can browse through the repositories listed in the Repository
> explorer nor I can update existing projects checked out with previous
> version of subclipse. Replacing the rc3 with version 102 causes that
> everything is functional again.
>
> I'm using subclipse with Eclipse 3.1.1 under Debian. Furthermore I use
> the JavaSVN adapter and I have to go through a proxy.
>
> Please let me know how I can assist you in a better way.
>
> Thanks a lot!
>
> Ciao,
> Sebastian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Jan 24 22:24:14 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.