Bug 69887 - [Wizards] Unable to share project with existing invalid connection method
Summary: [Wizards] Unable to share project with existing invalid connection method
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-07-12 19:31 EDT by Piotr Kaminski CLA
Modified: 2019-09-06 16:06 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr Kaminski CLA 2004-07-12 19:31:09 EDT
After upgrading to Eclipse 3.0 (clean workspace), I tried to add in my 
projects.  In Eclipse 2.1 I used a plugin to hook up to CVS using the extssh2 
method.  I'd like to switch to extssh with Eclipse 3.0.  However, when I try 
to "Share Project..." I first get told that the extssh2 method is not known 
(as expected), then get a "Project is already configured with CVS repository 
information" dialog that lists no connection information.  Clicking "Finish" 
pops up the same dialog, ad infinitum.  There seems to be no way to change the 
connection information or set up the connection from scratch.

Workaround:  Delete all CVS directories under project directory and re-import 
into workspace.
Comment 1 Michael Valenta CLA 2004-07-14 07:11:28 EDT
Another workaround would be to load the old plugin so that the old connection 
method is recognized. You could then perform a change sharing on the project or 
modify the repository location's properties before removing the old plugin.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:06:37 EDT
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.