Bug 461831 - Dependence not declared between "org.eclipse.papyrus.infra.emf" and "org.eclipse.papyrus.infra.services.edit"
Summary: Dependence not declared between "org.eclipse.papyrus.infra.emf" and "org.ecli...
Status: UNCONFIRMED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-10 10:46 EDT by Jonathan Dumont CLA
Modified: 2015-03-10 10:46 EDT (History)
0 users

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 Jonathan Dumont CLA 2015-03-10 10:46:17 EDT 
Hi,

In the same context than the #461711, I try to include some parts of Papyrus in a new RCP application.

Currently, I have to include "org.eclipse.papyrus.infra.emf". But when my application load, I have an error log : 
Errors occurred in parsing XML element type bindings contributed by plugin "org.eclipse.papyrus.infra.emf": client context "{0}" does not exist

It seems that the method ClientContextManager.configureBindings() tries to get the client context for the id org.eclipse.papyrus.infra.services.edit.TypeContext. However, this context is declared in an other plugin : "org.eclipse.papyrus.infra.services.edit".

Thus the question is : 
- Must "org.eclipse.papyrus.infra.emf" depends of "org.eclipse.papyrus.infra.services.edit" ?

There may be others solutions, I admit that I have not checked all what this can imply.

At this time, I will force the inclusion of "org.eclipse.papyrus.infra.services.edit" in my application, with its declared dependencies. This avoids the error.

Regards,

Jonathan