Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 398900

Summary: Prevent creating a project over an existing one
Product: [Eclipse Project] Platform Reporter: Christoph Pohl <christoph.pohl>
Component: IDEAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 Keywords: helpwanted
Version: 4.2.1   
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard: stalebug

Description Christoph Pohl CLA 2013-01-23 11:26:22 EST 
1. create a new general project "test1" in a non default location, e.g., c:\temp\test1
2. delete the project from your workspace but keep the project contents on disk
3. create a new general project "test2" in the same location c:\temp\test1

As is: You have a file c:\temp\test1\.project like this:
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
	<name>test1</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
	</buildSpec>
	<natures>
	</natures>
</projectDescription>

To be: 
a) get a warning upon 3) that there is a already an existing project in the way
b) if user confirms the warning, get a file like this:
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
	<name>test2</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
	</buildSpec>
	<natures>
	</natures>
</projectDescription>

This problem actually applies not only org.eclipse.ui.wizards.newresource.BasicNewProjectResourceWizard but probably all NewProjectWizards.
Comment 1 Lars Vogel CLA 2019-11-27 07:33:01 EST 
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.

If the bug is still relevant, please remove the stalebug whiteboard tag.