How to actually use locally-built Xtext? #3070
-
Hi, I've compiled Xtext on my machine but I'm having a hard time figuring out how to actually use the compiled artifacts. I've followed the instructions provided in This is what I tried doing afterwards. In Eclipse I opened the "Install new software" window, added a new repository, clicked on Archive and chose the After restarting the IDE I created a new sample Xtext project and generated its artifacts. However, when trying to launch the sample Xtext project as an Eclipse application, I see this error message: I am not sure what is causing this, since I performed a 100% vanilla build of Xtext (I have not modified a single line of code), and I am not sure how to proceed either. Any insight? |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 3 replies
-
Hi, that's something needed from the Eclipse LSP4E; you might want to add a recent Eclipse update and/or Orbit site so that you can install the missing feature. On a side note, for quickly manually testing your modifications to Xtext, if you did modifications in a workspace created with Oomph, it should be enough to start a new Eclipse instance from there. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Which version of Eclipse are you using? |
Beta Was this translation helpful? Give feedback.
-
And as I said, try to run another Eclipse instance from the Xtext workspace, if you want to do some quick manual checks |
Beta Was this translation helpful? Give feedback.
-
@LorenzoBettini I've set up the development environment using the Oomph automated configuration link. It installed Eclipse 2024-06. I am also seeing the issue with java processes using 100% of the CPU upon launching the DSL project, as you described in the issue you linked. |
Beta Was this translation helpful? Give feedback.
-
See my temporary local workaround in the above linked issue |
Beta Was this translation helpful? Give feedback.
See my temporary local workaround in the above linked issue