Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 495863

Summary: [1.9] [code completion] targetted module reference completion
Product: [Eclipse Project] JDT Reporter: Manoj N Palat <manoj.palat>
Component: CoreAssignee: Manoj N Palat <manoj.palat>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: jarthana
Version: 4.6   
Target Milestone: BETA J9   
Hardware: PC   
OS: Windows 7   
See Also: https://git.eclipse.org/r/75053
https://bugs.eclipse.org/bugs/show_bug.cgi?id=495801
Whiteboard:
Bug Depends on:    
Bug Blocks: 486988    

Description Manoj N Palat CLA 2016-06-10 06:20:24 EDT 
Targetted Module reference of exports is tied to the project dependency in general and module dependency specifically. This bug will be addressed completely once the dependency issues are sorted out.
Comment 1 Eclipse Genie CLA 2016-06-10 06:58:24 EDT 
New Gerrit change created: https://git.eclipse.org/r/75053
Comment 2 Manoj N Palat CLA 2016-06-10 07:20:31 EDT 
(In reply to Eclipse Genie from comment #1)
> New Gerrit change created: https://git.eclipse.org/r/75053

With the current model of one module-info per project, this patch determines the targets of all "opened" modinfos and creates the proposals accordingly. This would be revisited once we have more clarity on the namelookup of the modules based on final decision in bug 479483 especially the cyclic dependency issue brought out there.
Note: Bug 495818 itself should address the jdt.ui part of this bug as well - no separate jdt.ui bug envisaged as the target is a ModuleReference.