On 7/29/07, Ford, Kai P <kai.ford@aramco.com> wrote:
> I am referring to the user (me - fordkp) who created the repository,
> installed eclipse and subclipse, etc.
>
> Example:
> wangjx creates a new file within eclipse and commits it via eclipse
> team->commit menu option. The owner of the file in the subversion
> workspace is wangjx, but the Last Change Author is fordkp (INCORRECT).
> wangjx modifies an existing file within eclipse and commits it via
> eclipse team->commit menu option. The owner of the file is wangjx but
> the Last Change Author is fordkp (INCORRECT).
> wangjx modifies an existing file within eclipse and commits it via svn
> commit -m ... command line client. The owner of the file is wangjx and
> the Last Change Author is also wangjx (CORRECT).
>
> >
> > The key piece of info is the repository access method.
> > file://, https:// svn:// svn+ssh:// etc. I suspect you are
> > using svn+ssh.
>
> We are using svn://
svn:// will determine the author based on the credentials provided. I
would say that user wangjx is picking up cached credentials that have
your username and password. Given that the command line works
correctly (and JavaHL shares the same credentials cache as the command
line) then they must be using SVNKit. SVNKit caches credentials in
the Eclipse .keyring file. This is normally stored in the
configuration folder. Perhaps you zipped up your Eclipse installation
and shared it with others, or perhaps you are all using the same
installation? If it is the latter, then there are a bunch of command
line options you should be using when starting Eclipse so that each
user has certain files stored in their home folder.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Jul 29 15:37:37 2007