You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Import the example Xtext project (see below) in eclipse, and start a new runtime application.
Create a new file with the required extension (.mydsl) in a Sirius Modeling project.
Insert some parseable text inside the file (Hello world!) and save
Expected:
the Model Explorer should now show a tree view of the model content Actual result:
the file is still not recognised as a model and does not have a tree explorer (which would allow to easily create sirius representations)
Hi. Do you have the "Sirius Integration with Xtext" (org.eclipse.sirius.runtime.ide.xtext) feature installed in the environment where you see the bug? Depending on the Eclipse package you use it's not always installed (I'm not sure it is in the Eclipse Modeling package for example, and I think we do not install it by default either in Obeo Designer.
Video showing the issue: https://www.youtube.com/watch?v=RMzs0Wnz3Do
Steps to reproduce:
.mydsl
) in a Sirius Modeling project.Hello world!
) and saveExpected:
the Model Explorer should now show a tree view of the model content
Actual result:
the file is still not recognised as a model and does not have a tree explorer (which would allow to easily create sirius representations)
Tested with:
XText: 2.34.0
Eclipse Modeling Tools: 4.28.0
EMF: 2.34.0
Sirius: 7.3.0
Initially posted on the Xtext & EMF forum here.
The text was updated successfully, but these errors were encountered: