|Re: OCLinEcore does not work with Xtext 2.2.1 [message #798871 is a reply to message #798452]
||Wed, 15 February 2012 07:02
| Ed Willink
Registered: July 2009
"The editor class could not be instantiated" now has many more usual
reasons; most commonly in the case of Xtext, an Guice injection failure
throwing an exception during startup.
If you open the details tab you will find the 'reason'.
Caused by: com.google.inject.CreationException: Guice creation errors:
1) No implementation for org.eclipse.jface.viewers.ILabelProvider was bound.
amongst many others.
It would appear that Xtext 2.2.1 is not compatible with Indigo SR0
Xtext. https://bugs.eclipse.org/bugs/show_bug.cgi?id=371574 raised. A
problem with auto-generated APIs that are logically internal but
actually external since they form a contract between the runtime
supplied by Xtext and the editors developed with Xtext.
If the Xtext APIs have changed in one direction, they may also have
changed in the other, so we cannot fix it in OCL; we cannot change an
Indigo SR to have a higher Xtext minimum version. We will consider an
OCL (for Xtext 2.2.1) 3.1.2X release.
On 14/02/2012 18:06, Henrik Wivel wrote:
> To make a long story short, I ma getting this error message when
> trying to open a .ecore file using the OCLInEcore editor:
> "Could not open the editor: The editor class could not be
> instantiated. This usually indicates a missing no-arg constructor or
> that the editor's class name was mistyped in plugin.xml."
> I am using the latest Indigo distro from Itemis
> (xtext.itemis.com/xtext/language=en/36553/downloads), containing the
> latest version of Xtext2 (2.2.1.v201112130541) and it does not seem to
> work with OCLInEcore (3.1.1.v20110913-1213).
> Using the latest distro from Eclipse.org, everything works fine, but
> then I will be on Xtext2 ver 2.10, which I would like to avoid.
> Do any of you super intelligent persons out there have any ideas of
> what to do?
Powered by FUDForum
. Page generated in 0.02022 seconds