Community
Participate
Working Groups
20080424 - create the following 2 classes: package p3; public class B { class Inner { } } package p3; import p3.B.Inner; /** * {@link #foo(Inner)} * {@link #foo2(B)} */ public class A { public void foo(Inner inner) { } public void foo2(B b) { } } - open the AST view on 'Inner' in '#foo(Inner)': The node has no binding. Hover works. It also works for {@link #foo2(B)}, so I assume it has to do something with the inner class. The missing binding prevent linked rename to work correctly. Also the quick fix to add the missing qualification to Inner (if compliance == 1.4) doesn't show up.
Inner' in '#foo(Inner)' node has no binding as soon as compliance is 1.4. Bindings are ok for compliance > 1.4 bug introduced at 3.4 M3 while fixing bug 195374
Created attachment 101038 [details] [proposed patch + test case] on top v865
(In reply to comment #2) with this fix: - still report the unresolved reference at 1.4 compliance as requested by bug 195374 - resolve the bindings
(In reply to comment #2) passes all jdt.core, ui and text tests
Since this is a regression comparing to 3.3.2, and the patch is quite simple, we should target it for 3.4RC2. Eric, please ask for the reviews of the patch.
Frederic, may you please review proposed correction? thanks
(In reply to comment #6) Jerome, may you also please review? thanks
Patch looks good: +1 However, while reviewing the patch, I discovered a problem on the fix released for the initial bug 195374. The types partially qualified are warned by the javadoc tool but not by the JDT compiler. I have opened bug 233187 for this issue...
Patch looks good: +1
patch released in HEAD for 3.4RC2
(refresh issue)
Verified for 3.4RC2 using I20080523-0100.