Community
Participate
Working Groups
I created a synchronized project I deleted the project in my local workspace. I deleted the directory on the remote system too. I checked out the code again into a new project with the same name as the first When I try to Convert to Synchronized Project it does not include this new project in the list of potential projects to convert It is as if the information about the previously sync'd project still exists How to workaround for now, and can this be fixed?
I don't see this behavior: 1. Create a new C project 2. Convert the project to a sync project 3. Delete the project 4. Create a new C project with the same name 5. Convert the project to a sync project It's possible this is something to do with CVS, which I assume is what you mean by "checked out the code again".
Yes I checked the project out from CVS both times
Please try the above scenario to see if it is CVS causing the problem.
The second time, did you create a new C project or only checkout from CVS (without using the new project wizard)? Only local C, C++, and Fortran projects can be converted to synchronized projects. Thus, you have to convert to a C project first and then convert to a sync project.
I just tried the following scenario: 1. Check out a new C project from CVS (using wizard) 2. Convert the project to a sync project 3. Delete the project 4. Check out a new C project from CVS (using wizard), same name as #1 5. Convert the project to a sync project The wizard in step #5 shows the project, so the behavior you saw may be related to John's comment. I haven't tried that. However, on step #4, as soon I clicked on the project *in the CVS Repository Exploring Perspective*, I got 6 errors logged: Unable to get project from the org.eclipse.ptp.rdt.sync.ui plugin (at least that's what the error log says). There was no stack trace.
I wasn't able to reproduce Greg's error. The "Unable to get project" message, though, is only printed by SyncMenuOperation, which controls the sync context menu. The message is printed if it cannot get the project corresponding to the currently selected resource...
I think the behavior Greg experienced may be related to bug 359907, which I just filed. If a new non-sync project is created with the same name as a deleted sync project, that project will have the sync nature. This causes numerous problems...
Bug 360170 may also be related. Note, though, that 359907 and 360170 are distinct, because one happens when not deleting contents on disk, while the other requires that this option be selected.
