Community
Participate
Working Groups
Created attachment 177619 [details] example project I20100824-1210 The Eclipse compiler can't build projects with package names that only differ in case: The project was not built due to "A resource exists with a different case: '/CaseSensitive/bin/pack'.". Fix the problem, then try refreshing this project and building it since it may be inconsistent Javac happily compiles this and java.exe runs it (see the ANT script in the attached example).
I think the problem comes from the fact that this happens inside the workspace which itself is case-sensitive, hence writing to the same bin folder fails. If the source folders get different output folders then it works.
Srikanth, this seems like a close relative of bug 321115?
(In reply to comment #1) > I think the problem comes from the fact that this happens inside the workspace > which itself is case-sensitive, hence writing to the same bin folder fails. If > the source folders get different output folders then it works. Yes. Since the workspace itself is backed by a file system that is not case sensitive, there isn't much that can be done. Unless the platform layer wants to invest in coming up with special file name encodings to avoid this problem. IMO, this is not worth pursuing. Markus, I am inclined to close it as WONTFIX. Do you disagree ?
This is a long standing issue. See also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=25148 https://bugs.eclipse.org/bugs/show_bug.cgi?id=25406 https://bugs.eclipse.org/bugs/show_bug.cgi?id=123684 https://bugs.eclipse.org/bugs/show_bug.cgi?id=97401
Note that the given example compiles and runs fine with javac. If there's no real conflict (i.e. just packages with different casing), then I would expect this to work in Eclipse as well. Low priority, though. Filename mangling for clashing *type* names would be overkill, given that javac also doesn't do that.
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. -- The automated Eclipse Genie.
