Summary: | FUP of bug 361938: Other error code pattern | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Satyam Kandula <satyam.kandula> | ||||
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | minor | ||||||
Priority: | P3 | CC: | srikanth_sankaran, stephan.herrmann | ||||
Version: | 3.8 | ||||||
Target Milestone: | 3.8 M5 | ||||||
Hardware: | PC | ||||||
OS: | Windows 7 | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Satyam Kandula
2011-12-05 08:30:51 EST
Created attachment 209772 [details]
Proposed fix + regression test
Sorry, I didn't pay closer attention to earlier. The fix for bug 361938 is not appropriate and works only because there are two bugs now that somewhat cancel out each other. Patch & tests released for 3.8 M5 via http://git.eclipse.org/c/jdt/eclipse.jdt.core.git/commit/?id=eb40a119cd5ecacf8e90c38261ec37c99b5a07b7. I'll leave the maintenance branches as they are. The API doesn't do what the javadoc claims in the case of a badly broken client that looks up resources in pre java mode, but that is unlikely scenario and it is late for 3.7.2 Verified for 3.8 M5 by code inspection. |