Community
Participate
Working Groups
Build Identifier: 20090621-0832 After changes in our cvs system I had to change the location of the cvs server. Unfortunately I had already imported a new project that was in this new CVS server, which cause it to be already available in the CVS Repositories list. When I tried to move the old cvs location to the new one following these steps [http://help.eclipse.org/ganymede/topic/org.eclipse.platform.doc.user/tasks/tasks-95.htm Eclipse Help] I got an error message saying that it was a duplicated location. Ideally I should be able to move the old location to the new one even if it is already available. Or I should be able to chose the CVS repository of the project. Reproducible: Always Steps to Reproduce: 1.Import a project from CVS Repository A 2.follow steps in http://help.eclipse.org/ganymede/topic/org.eclipse.platform.doc.user/tasks to move CVS location from B to A
> Or I should be able to chose the CVS repository of the project. You can do that by going to project's properties, than to CVS group. There is "Change Sharing" button which allows you to switch project to a different repo. However, this would work for 3 repos but not for a dozen. I guess an option here would be showing a similar dialog when removing an old repo. The dialog would allow you switch all projects from the old repo being removed to the selected one (most probably a compatible one). The problem is that the new repo would have to be valid for all the projects... which I can imagine is not always the case.
Thx for the reply, good to learn something new :) But I do agree with your proposal. The current solution does not scale well with the number of projects.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
