Bug 1943

Summary:	Allowed to create 2 projects with same name, different casing (1GCSSJB)
Product:	[Eclipse Project] Platform	Reporter:	Karice McIntyre <Karice_McIntyre>
Component:	UI	Assignee:	Ryan Cooper <ryan_cooper>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	simon_arsenault
Version:	2.0	Keywords:	usability
Target Milestone:	2.0 M3
Hardware:	All
OS:	Windows 2000
Whiteboard:
Bug Depends on:	3076, 3140
Bug Blocks:

Description Karice McIntyre

2001-10-10 22:22:47 EDT

The UI allows me to create 2 projects with the same name but different casing.

Steps:
Create project named 'Test'
Create project named 'test'

They appear as 2 distinct projects but will share the same directory.

NOTES:

KH (5/4/2001 2:30:31 PM)
	Core issue

Comment 1 Karice McIntyre

2001-10-19 16:32:09 EDT

As of v205 Core has resolved the issue since you can no longer create a project 
with the same name but different casing on windows.

However, the UI is inconsistent because if you create a project named 'Test' 
then try to create another project named 'Test' the UI will tell you in the 
title area that you are in error.  However if (after creating project 'Test') i 
try to create a project named 'test' I do not see an error in the title area.  
I have to hit Finish to get the error message back (from Core, I assume) 
telling me that a resource named /Test already exists.  shouldn't the UI be 
able to tell the user in the title area of the dialog that 'test' is already 
the name of an existing project?

Comment 2 DJ Houghton

2001-10-29 17:40:39 EST

PRODUCT VERSION:
047a

Comment 3 Simon Arsenault

2002-01-28 10:38:05 EST

Find out what is going on. Why is the error message so late?

Comment 4 John Arthorne

2002-01-29 13:14:33 EST

The short answer is: we don't do eager validation of case variant collisions 
because it is not a state that can easily be detected beforehand. It requires 
file system I/O, but the eager validation methods (IWorkspace#validatePath and 
IResource#exists()) are designed to be workspace-based, not file-system based.

The long answer is an RFC:

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core-home/rfc/0
001/index.html

Comment 5 Simon Arsenault

2002-02-01 16:38:52 EST

We now check for the case variance errors and display a more appropriate error 
message. Fix in build > 2002-02-01