Thanks for the suggestions Mark.
> Try disconnecting your projects. Team > Disconnect. Leave
> the .svn metadata in tact.
> Then delete all the repository locations for argouml and
> re-add it. Then do Team > Share again. It should recognize
> the .svn folders and just connect it up to the repository you created.
I had tried this with one project before, without success, but the key was
to disconnect all the projects which were connected to the bogus repository
definition so that it could be deleted. I just deleted the one repository
location which was too high up in the hierarchy and then re-shared
> OR even easier is to just right-click on each repository
> location and do Properties then set the root URL. This is
> actually how it probably got a wrong value to begin with.
I should have mentioned that I already tried this and it only allows you to
browse to the same URL or its parent. ie http://argouml.tigris.org or
http://argouml.tigris.org/svn when the current URL is
Most of the projects in this workspace were created from an Eclipse Project
Set File and have "branch" decorations which are the fully specified URL (eg
"http://argouml.tigris.org/svn/argouml/trunk/src/model" instead of
"trunk/src/model" which looks a little weird but appears to just be a
My best guess as to how this got messed up is that I created a repository
location definition for "http://argouml.tigris.org/svn", found it didn't
work, but didn't delete it, created another for
"http://argouml.tigris.org/svn/argouml" and then at some point, perhaps when
switching branches for a project, Subclipse decided to pick the higher level
root which only partially works. It should probably exclude from
consideration any location which doesn't meet its requirements. That
scenario could easily be wrong though because it's been messed up for a
couple of weeks and I've just been living with it since I could still get
Thanks again for getting my workspace sorted out.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Aug 22 18:45:58 2007