| Summary: | [resources] Unexpected CASE_VARIANT_EXISTS errors | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Simon Arsenault <simon_arsenault> |
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Simon Arsenault
The method will fail because a case variant in the workspace already exists. What is the behaviour that you expect? I thought the case variant stuff only applied to the actual file system directory specified for the location. That the workspace itself was case sensitive. Am I correct to say that on Linux, this scenario is permitted, but not on Windows because this OS is case insensitive - even though the limitation in this scenario is imposed by the workspace, not the file system of the OS? We (ui team) need to understand how this works and what are the limitation so we can find a way to show this to the user - it will not be obvious to the user this scenario is not allowed. I discussed this with Simon on Friday and it seems to be a bug. Since the two projects are in different locations, there is no filesytem collision so we should allow it. . Closed by accident, reopening... DJ, I thought you might want to take a look at this since you've completely rewritten that code. Still a problem in build 2002-04-09. We should allow different casing in the workspace if the user is not using the default content area. Investigate complexity to fix to see if it is reasonable for 2.0. Still a problem with build i1026. Even thought it's technically possible to create these two projects, we can't allow it. We store several types of meta-data on a per-project basis in the local file system (.projects directory, .history directory). These metadata directories would collide if we allowed both of those projects to exist. Closing as won't fix. |