Bug 439669 - MethodProposalInfo can't resolve members when declaring type is not in global(default) package.
Summary: MethodProposalInfo can't resolve members when declaring type is not in global...
Status: NEW
Alias: None
Product: JSDT
Classification: WebTools
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Chris Jaun CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-16 00:50 EDT by Jeeeyul Lee CLA
Modified: 2014-07-16 00:50 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeeeyul Lee CLA 2014-07-16 00:50:15 EDT 
org.eclipse.wst.jsdt.internal.ui.text.java.MethodProposalInfo.resolveMember() is searching members using declaring type name. (It means, simple type name without package).

What if we have xxx.Person (xxx is package) and it has a method xxx.Person.test(); And this method has a well formed JSDoc comment.

However, MethodProposalInfo trying to find Person.test(), as a result, completion proposal info is not showing up.

Using getDeclarationSignature() instead of getDeclarationTypeName() simply can fix this problem. (I tested it with changing value in debugging context)