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

[Subclipse-users] RE: UserInfo in Repository URL is Ignored

From: TMate Software Support <support_at_tmatesoft.com>
Date: 2006-08-03 16:07:14 CEST

Hello Craig,

Thanks for reporting this problem. I will fix it soon, so that username from
the URL will be used as a default SSH login name.

After user is succesfully authenticated against SSH server, user is prompted
for "author" name, i.e. name of the user that will be used for commit
operations. This name may differ from SSH login name. In Subclipse 1.1.4
there is no dedicated username prompt dialog, so password dialog is reused.
You may left password field empty in it.

> 4) A Repository Password window appears. The top field is labeled
> "Repository:, and contains something like:
>
> svn+ssh://server.isi.edu
I consider this as correct behaviour: at this point user is prompted to
provide credentials to log in over SSH into the server, so only server's
host name is displayed.

> I also have access to a Windows XP system with Eclipse
> 3.2, using the JavaHL SVN Interface. It correctly connects
> to the SVN server, without passing though a repository
> password dialog box.
JavaHL uses "tunnel" definition (starts external program) defined in
Subversion config file. JavaSVN also supports "tunnels", but only when
tunnel name differs from "ssh", for instance one may define "xssh" tunnel
and URLs will look like svn+xssh://.... Name of the user for svn commits
will also be prompted however.

Alexander Kitaev.

> -----Original Message-----
> From: Craig Milo Rogers [mailto:rogers@isi.edu]
> Sent: Thursday, August 03, 2006 5:48 PM
> To: users@subclipse.tigris.org; feedback@tmatesoft.com
> Subject: UserInfo in Repository URL is Ignored
>
> There is a bug in subclipse or in javasvn; I don't know which.
> General configuration:
>
> 1) SuSE Linux 10.1, x86_64
>
> 2) Eclipse 3.2
>
> 3) Subclipse 1.0.3
>
> 4) javasvn from subclipse or 1.1.0beta4 from the web site
>
>
> Steps to reproduce the problem after installing
> Subclipse and JavaSVN:
>
> 0) Ensure that Window->Preferences->Team->SVN->SVN Interface is
> set to JavaSVN.
>
> 1) Eclipse menu: Window -> Open Perspective -> Other
> Select SVN Repository Viewing.
>
> 2) In the SVN Repository window:
> context right click -> new -> repository location
>
> 3) The "Add a new SVN Repository" window appears. Enter a Location
> URL such as:
>
> svn+ssh://serveruser@server.isi.edu/path/to/repository
>
> where <serveruser> is different from the username on
> the workstation
> running Eclipse.
>
> Click Finish.
>
> 4) A Repository Password window appears. The top field is labeled
> "Repository:, and contains something like:
>
> svn+ssh://server.isi.edu
>
> The next field is labeled "Username:", and ought to contain
> the <serveruser> entered in the URL in (3). Instead, it
> contains the username of the user on the workstation running
> Eclipse. This is the bug.
>
>
> If is necessary to replace the username in this form with the
> <serveruser> value in order to eventually connect to the
> SVN server.
>
>
> I must confess, I just spent several fruitless hours
> staring at the source code for both subclipse and javasvn. I
> attempted some changes in the javasvn file
> JavaHLAuthenticationProvider.java (see
> attachment) without apparent success. It is possible that
> Subclipse is setting the username before calling JavaSVN.
>
> I also have access to a Windows XP system with Eclipse
> 3.2, using the JavaHL SVN Interface. It correctly connects
> to the SVN server, without passing though a repository
> password dialog box.
>
> Craig Milo Rogers
>
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Aug 3 16:08: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.