Hi,
Our developers work in pairs, and switch machines often. Because of
the way SVN credentials are managed, this has the unfortunate side
effect of there being no great way (as far as I've found) of having
changesets marked as being checked in by one member of the pair.
Instead, all changesets from a particular machine are checked under
whatever username happened to set up the SVN connection in subclipse.
I've only found out a few ways of switching the credentials after the
repository connection has been setup:
Don't check the remember credentials button when first prompted for
SVN authentication information. This has the effect of being asked
every time you do anything with SVN: browsing the repository, checking
in, checking out, etc. Not great, because this ends up really asking
too often.
Delete the SVN credentials from the keyring where they're stored. Not
really user friendly.
Set up a slightly different SVN repository for each user so that we
fool Subclipse into different credentials for the same repository. I
think the only way to do this is setup many different server names for
the same server, which is a bit of a pain.
I'm wondering if someone has come up with a nicer way of handling this
sort of work environment with Subclipse? What I'd really like is to
have the user login when they open eclipse or at least on first
interaction with SVN, basically eclipse-lifetime scoped credentials.
But I'd be happy if, for example, there was a way to do this with
separate eclipse workspaces for each set of credentials.
Any advice is welcome!
Thanks,
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-07-02 18:37:00 CEST