Community
Participate
Working Groups
When a project gets moved to another location, Eclipse IDE still shows the project name there. Its a minor issue, however it seems more convenient if it gets automatically removed when project path is not found.
Do you mean that the name doesn't change when it is moved? Or that there are some leftover files?
Created attachment 81793 [details] Example
i think simran means when you move the project to another folder, and reopen eclipse, the Project name will still appear on the work bench. however you cannot open it or do anything with it just sits there. For example in that screen shot, CardDeck project was move to another folder, now it just sits there and cannot do anything. To put it back into ya workbench ya will need to remove the CardDeck then re-import it. Instead maybe it can be removed automatically, or maybe can stick in a button on the problem occurred dialogs saying "browse for project"?
(In reply to comment #3) > i think simran means when you move the project to another folder, and reopen > eclipse, the Project name will still appear on the work bench. > however you cannot open it or do anything with it just sits there. I think this is what simran meant as well. This is something for Platform/Resources to deal with. I guess the basic request is that if the project's physical folder is (re)moved that the IWorkspaceRoot inherently delete the IProject as well. > Instead maybe it can be removed automatically, or maybe can stick in a button > on the problem occurred dialogs saying "browse for project"? Or this could be an option. I admit that it's confusing for new users and is something that I've gotten used to over the many moons that I've used Eclipse for.
Created attachment 81795 [details] Sample deletion dialog if that is so, then that should something the refresh should handle imho. and it does. Refresh the workspace, and you will have a dialog poping up offereing you to delete the ghost project.
I think the real problem is that our error reporting could be better and should have an idea of how to resolve the issue.
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.
