| Summary: | SharedStateModule should not have priority over LanguageSpecificModules | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Moritz Eysholdt <moritz.eysholdt> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jan, sebastian.zarnekow |
| Version: | 1.0.0 | Flags: | jan:
indigo+
|
| Target Milestone: | M2 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
Done. Closing bug which were set to RESOLVED before Eclipse Neon.0. |
Currently, a lanugage's Activator gives priority of the SharedStateModules over a a language's RuntimeModule and UIModule. Therefore, a language can not override the bindings provided by the SharedStateModule. injectors.put("foo", Guice.createInjector(Modules.override(Modules.override(getRuntimeModule("foo")).with(getUiModule("foo"))).with(getSharedStateModule()))); It would be better if the language specific modules would have priority over the SharedStateModule since this would allow for easier language-specific-customization of global services.