Summary: | Quick hierarchy: chosen method is not always selected | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | David Saff <david> |
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | minor | ||
Priority: | P3 | ||
Version: | 3.1 | ||
Target Milestone: | 3.3 RC4 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
David Saff
2005-06-20 05:30:14 EDT
might be related to bug 100565 This is absolutely strange. I have one workspace wheree process environment does show up as a subclass of HashMap in this case and one where it doesn't. Both projects are 5.0. Dirk, Exact same JDK's? Actually, the problem is that the source range for the method put in ProcessEnvironment is [-1,0]. Additionally the signature of the put method is java.lang.Object put(java.lang.Object, java.lang.Object) whereas the method should be Object put(String, String). Moving to JDT/Core. When trying to reproduce please be aware of bug 100839. Cannot reproduce using 3.3 RC4 whatever the combination used for projects compliance and JRE... |