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

Bug 93229

Summary:	[model] Rename package is NOT ALWAYS case sensitive under windows.
Product:	[Eclipse Project] JDT	Reporter:	spiker <spiker_h>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	dytyniak
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description spiker

2005-04-29 02:11:47 EDT

Given a package structure "first.second.last".
When we rename package "last" to different case, everything is fine. But when 
we rename package "second" to "Second", eclipse will show the following error 
message:
---------------
An exception has been caught while processing the refactoring 'Rename 
package 'first.second.last' to 'first.Second.last''

Reason:
A resource exists with a different case:/test/src/first/second.
---------------

Comment 1 Frederic Fusier

2005-04-29 07:01:51 EDT

Problem comes from
CopyResourceElementsOperation.createNeededPackageFragments(...) method. At line
155 createFolder raises a JavaModelException which wrappes following
CoreException (code 275):
"A resource exists with a different case: /b93229/first/Second."

Comment 2 Jerome Lanneluc

2007-06-19 10:56:19 EDT

To be investigated for 3.4

Comment 3 Bob Dytyniak

2008-01-28 19:20:48 EST

A much simpler example in Eclipse 3.2.2 in Win XP Pro (this was not a problem in Eclipse 3.0.x):

Plain old java project named:

lowerCaseJavaProject  //lower case 1st letter "l"

Do Refactor > Rename to:

LowerCaseJavaProject //1st letter changed to Upper case "L"

and you get the 
Dialog: Rename Java Project
reporting the error:

"A folder with that name already exists"

Comment 4 Jerome Lanneluc

2008-05-12 05:21:09 EDT

We ran out of time for 3.4. Deferring

Comment 5 Eclipse Genie

2020-02-01 10:31:36 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.