Community
Participate
Working Groups
I20060215-0010 Content Assist should give constants declared in target type higher relevance, since constants from supertypes would lead to warnings anyway. Example: I have org.eclipse.jdt.core.compiler.CategorizedProblem imported and invoke content assist after this: int bla= CategorizedProblem. Expected: all the CAT_* proposals for constants from CategorizedProblem should come first; constants from the superinterface IProblem come after Was: all constants sorted alphabetically
adapted summary: this is true for static methods as well.
This would be a great 3.3 enhancement ;-)
Created attachment 45739 [details] Proposed patch This patch give an higher relevance to static fields and methods declared in target type when the completed node is a qualified name. Member types have always this higher relevance otherwise the relevance for fields and method would be always higher.
Released for 3.3 M1. Test added CompletionTest#testStaticMembers1()
Verified for 3.3 M1 using build I20060804-0010.