Summary: | Can't have different case package names | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Michael <mdcoughlin> | ||||
Component: | Core | Assignee: | Kent Johnson <kent_johnson> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | minor | ||||||
Priority: | P3 | CC: | jerome_lanneluc | ||||
Version: | 2.0 | ||||||
Target Milestone: | 2.1 M4 | ||||||
Hardware: | PC | ||||||
OS: | other | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Michael
2002-10-21 16:38:14 EDT
This message is generated from jdt.internal.core. Under what circumstances is this marker created? When the "A" package is created in the "bin" folder after the "a" package has already been created, I presume that a CoreException is thrown. Pls investigate Created attachment 2287 [details]
Contains a regression test for this bug (testDiffererentCasePackageAndClass)
Kent, once this bug is fixed, could you please release the attached tests.
We cannot support packages named 'a' & 'A'. The new test assumes we can. We receive a ResourceException when we try to create a folder for the second package, the message is: 'A resource exists with a different case: /Project/bin/p.' Possibly we could integrate CoreException error messages with our message. The idea was to catch and ignore this exception if its code is IResourceStatus.CASE_VARIANT_EXISTS. But we cannot successfully build the example. The compiler does not consider the 2 packages to be equal. The best we can do is improve the error message. Changed our error message... we now incorporate the CoreException's error message so the user has a better idea what the problem was. Verified. |