Community
Participate
Working Groups
The diagram project shows an error: org.eclipse.gmf.runtime.diagram.ui.editpolicies.LayoutEditPolicy cannot be resolved to a type SimpleTypeEditPart.java /org.eclipse.xtext.example.gmf.diagram/src/org/eclipse/xtext/example/gmf/diagram/edit/parts line 72 Java Problem Replace by: org.eclipse.gef.editpolicies.LayoutEditPolicy solves the problem and makes the example work.
Not on my machine. Everything compiles fine as is. The code is working withGMF 2.3 RC2, which was kind of a hassle to install. Have you installed GMF Tooling, GMF Runtime and GMF Notation completely, i.e. with all dependencies? Did you regenerate the gmfgen model or the diagram code? AFAIR, org.eclipse.gmf.runtime.diagram.ui.editpolicies.LayoutEditPolicy has been around since the beginnings of GMF (and still is), so it looks like a missing dependency. The GEF version is a superclass lacking some essential functionality, so this should not be a valid replacement.
Hello, I use Galileo Modeling RC2. GMF is allready installed in this distribution. Generating the diagram project (models project model -> Entities.gmfgen -> Contextmenu -> 'Generate diagram code) solves the problem. (In reply to comment #1) > Not on my machine. Everything compiles fine as is. The code is working withGMF > 2.3 RC2, which was kind of a hassle to install. > > Have you installed GMF Tooling, GMF Runtime and GMF Notation completely, i.e. > with all dependencies? Did you regenerate the gmfgen model or the diagram code? > > AFAIR, org.eclipse.gmf.runtime.diagram.ui.editpolicies.LayoutEditPolicy has > been around since the beginnings of GMF (and still is), so it looks like a > missing dependency. The GEF version is a superclass lacking some essential > functionality, so this should not be a valid replacement.
This happens when you try to run code generated with GMF 2.3 in a GMF 2.2 environment. To get rid of the error you have to regenerate the diagram code by choosing "Generate diagram code" from the context menu of the gmfgen model. I added a section on this in the docs. Closing this issue.
Closing bug which were set to RESOLVED before Eclipse Neon.0.