> Well, I can assure you that I was using the username "svn"
> and a private key for "ijuma" and the server has all commits
> with the username "ijuma". However, on the server side,
> "svnserve --tunner-user" is used. Perhaps this is the difference?
So from your description it looks like "ijuma" name was used both for SSH
login and Subversion commit, and what I'm talking about is that version of
JavaSVN used in Subclipse 1.1.x allows one to use different names. Indeed it
starts "svnserve" with --tunnel-user option now in case SSH and svn username
differs.
Of course one could do the same with JavaHL and with manula configuration of
ssh or plink client program.
> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Ismael Juma
> Sent: Tuesday, July 18, 2006 3:26 PM
> To: users@subclipse.tigris.org
> Subject: Re: [Subclipse-users] Possible bug when using svn+ssh.
>
> Alexander Kitaev <alex <at> tmate.org> writes:
> > No, it was not. User name in the first dialog was used both for ssh
> > login and for commit. The only way to override last one was to set
> > system property "javasvn.ssh.author" (in version 1.0.3 of
> Subclipse),
> > now this additonal dialog pops up.
> [...]
>
> Well, I can assure you that I was using the username "svn"
> and a private key for "ijuma" and the server has all commits
> with the username "ijuma". However, on the server side,
> "svnserve --tunner-user" is used. Perhaps this is the difference?
>
> Ismael
>
> ---------------------------------------------------------------------
> 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 Jul 18 13:49:40 2006