Bug 488094 - Make Sirius completion based on registered meta-model for every interpreter
Summary: Make Sirius completion based on registered meta-model for every interpreter
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 3.1.0   Edit
Hardware: All All
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks: 481849
  Show dependency tree
 
Reported: 2016-02-19 06:07 EST by Laurent Fasani CLA
Modified: 2017-02-21 05:13 EST (History)
2 users (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 Laurent Fasani CLA 2016-02-19 06:07:57 EST 
the bug 481849 is the first step to have only RepresentationDescription meta-models in the scope of validation, completion and runtime.
That bug handle the validation aspects.
This ticket is about completion aspect.

The 
org.eclipse.sirius.common.tools.api.interpreter.JavaExtensionsManager.reloadEPackages() method add EPackage found in the VSP dependecies.

JavaExtensionsManager is instanciated by AcceleoAbstractInterpreter and ServiceInterpreter that are IInterpreter.
These IInterpreter are created(indirectly) by the singleton CompoundInterpreter.INSTANCE.

The problem is the CompoundInterpreter is used for completion and for the runtime as well.
Finally, the question handle this ticket is how to manage the JavaExtensionsManager behavior for completion but not for run-time.
Gooluck.
Comment 1 Laurent Fasani CLA 2016-02-23 09:56:48 EST 
the solution of this the ticket will probably be the same as in bug 488299