Community
Participate
Working Groups
Using 0518, the name of a method ref inside a javadoc comment resolves to a method binding instead of a type binding. The name (selector) of method invocation should not resolve to a binding. It should return null. Right now it returns a method binding.
Reconsider post 3.0.
Reopen to set as duplicate...
*** This bug has been marked as a duplicate of 54948 ***
Fixes for this bug and bug 54948 are in the same area, but they cannot be considered as duplicate... So, reopen to change state.
Patch is ready. I'll attach it when bug 63044 fix will be released as change is in the same area...
Synchronize bug state to dependent...
Should we fix it for 3.0.1?
Actually, after further thinking, we may keep existing behavior if redundant information is useful for clients. Pretty much like redundancies with qualified names (each individual name carries a binding).
Will be fixed at the same time as bug 62605
Reopen as LATER is deprecated...
No action planned for this problem as it does no longer occur when bug 62650 will be fixed... => Close as WONTFIX.