Bug 45255 - same resource exists with different case
Summary: same resource exists with different case
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: 3.0 M5   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-21 03:50 EDT by Luca Di Stefano CLA
Modified: 2003-11-14 07:26 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luca Di Stefano CLA 2003-10-21 03:50:22 EDT
I have a java project with two src directories.
The first srcA contains a class file com/pippo/pluto/A.java, the second srcB
contains com/pippo/Pluto/B.java.
The project cannot be compiled because the same resource is found (packages
com/pippo/pluto, com/pippo/Pluto)
Comment 1 Kent Johnson CLA 2003-10-21 11:49:08 EDT
So why do you think that this is a bug?

The file system doesn't allow us to create 2 directories with the same name but 
different case.

You need to change one of the names.
Comment 2 Luca Di Stefano CLA 2003-10-21 12:01:42 EDT
java is able to handle package that differs only for cases, that should be
supported by eclipse jdt core too, else it is not fully compatible with java
compiler.

that is not a blocker ticket because there are some workarounds, like create two
dependent java projects, then eclipse works fine without errors

what do you think ? ;-))
Comment 3 Luca Di Stefano CLA 2003-10-21 12:03:31 EDT
>The file system doesn't allow us to create 2 directories with the same name but 
>different case.

they are not in the same fs:
project
   srcA/com/pippo/pluto/A.java
   srcB/com/pippo/Pluto/B.java
Comment 4 Kent Johnson CLA 2003-10-21 12:06:54 EDT
This isn't a JDT core limitation.

No Java compiler successfully compiles this code because we all receive the 
same error when we try to write out the .class files.

The .class files are written to the same output folder. That is where the 
collision occurs.

You can configure your source folders to have their own output folders, but you 
should seriously consider renaming one of the packages.