Bugzilla – Full Text Bug Listing
| Summary: | Open declaration fails on generic methods when target classfile compliance=1.4 and selected jre=1.5 | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Khaled Agrama <kagrama> |
| Component: | Core | Assignee: | Srikanth Sankaran <srikanth_sankaran> |
| Status: | VERIFIED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | amj87.iitr, Arne.Christensen, daniel_megert, markus.kell.r, Olivier_Thomann, srikanth_sankaran |
| Version: | 3.1 | ||
| Target Milestone: | 3.7 M4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
FYI I'm running build I200412070800. SelectionEngine resolve the method Set#containAll(Collection) and the java model contains the method Set#containAll(Collection<?>). These methods are not identical but are similar. We could return similar methods if there is no exact match. This problem also exists in build I20060223-1656 This mixed mode problem dates back to at least 2004. This bug is not reproducible anymore on HEAD, is reproducible on I20101025-1800. Closing as duplicate of 299384 *** This bug has been marked as a duplicate of bug 299384 *** Verified for 3.7M4 using build I20101205-2000. Verified using I20101207-0250 (4.1 I-build) |
Reproduction: 1. Go to preferences and change java compiler compliance to 1.4. Select JDK 1.5 as your JRE. 2. Create a new project and add the following class: public class TestClass { void doSomething() { Set x = new HashSet(); x.containsAll(new HashSet()); } } 3. Position the cursor on the containsAll call and press F3. Notice that the open declaration does not work. If you move the compliance to 1.5 or select a 1.4 JRE, it will work.