Dan North <email@example.com> wrote on 07/27/2005 10:05:19 AM:
> Not sure what to do with these or if they are already in the bug
> from me and one from someone in my team:
> 1. Incorrect repository password is not replaced with correct one.
> - The user defines a svn repository and enters an incorrect password.
> connection fails, but they choose to keep the connection anyway.
> - Every time they click on something on the repository view, it asks for
> password, but doesn't replace the bogus one, so they have to keep
> Workaround: delete the repository definition and try again.
Now that we support prompting of passwords from JavaHL. The best thing is
to never enter any username or password credentials in the connection.
JavaHL will then take care of everything. The issue here is that our
username and password is invalid, so JavaHL is prompting for a new one.
But we do not really have any way to go update ours.
> 2. Checking out a project from svn
> - Start checking out
> - Realise it's the wrong thing (!)
> - Click on cancel
> - Firstly, it just keeps checking everything out anyway. Secondly, it
> sits there chugging for ages and eventually runs out of memory (with
We do not currently have any way to cancel any svn operation once it
starts. There is an issue for that already. Note that if you are using
http:// then svn itself currently has no way to cancel a transaction
anyway. That will be fixed in a future version when they upgrade to a
newer version of Neon.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Thu Jul 28 00:09:51 2005