|
|
|
|
Re: IncQuery support for XText 2.5 [message #1235487 is a reply to message #1235265] |
Fri, 24 January 2014 13:47 |
Zoltan Ujhelyi Messages: 392 Registered: July 2015 |
Senior Member |
|
|
Hi,
at the point István made his statement, we were functioning well with the current Xtext 2.5 snapshots. Sadly, a change before release broke our tooling (as reported in https://bugs.eclipse.org/bugs/show_bug.cgi?id=424535). Additionally, we have some builder issues as well (https://bugs.eclipse.org/bugs/show_bug.cgi?id=419128), however those are at least workaroundable. So, currently not even CI/master works with Xtext 2.5.
I am in the middle of a quite big refactoring (but luckily the end should be close) related to our builder infrastructure and the generated code, that will help us to decouple our engine from Xtext, making the generated patterns code work without Xtext even installed, while providing a builder architecture closer to what Xtext is supporting directly, so I hope, we could support Xtext 2.5 soon (in a few weeks).
I will report back when I have some concrete results.
Cheers,
Zoltán
|
|
|
|
Re: IncQuery support for XText 2.5 [message #1235835 is a reply to message #1235636] |
Sat, 25 January 2014 12:23 |
Zoltan Ujhelyi Messages: 392 Registered: July 2015 |
Senior Member |
|
|
Hi Emre,
we regularly test our code with Xtext 2.4.3 (and 2.4.2 should work as well), so both the latest 0.7.x releases and our 0.8 M1 milestone should work well with this version.
Additionally, we try to build some compatibility versions with Xtext 2.3 (current version needs a different download, but for that we do not have a public download url yet), but if the version of Xtext does not matter to you, I suggest using version 2.4 (it is noticeably faster than the older versions in several environment).
About 2.5: sadly the eiq editor cannot be opened at all, and I believe some other parts are erroneous as well in the tooling, so I think it is safe to assume it is completely unusable. I am not sure about the runtime: it might or might not work.
I tried to provide a quick workaround when the issue came forth, but sadly I did not find any, so I postponed the issue until the refactoring is finished.
Cheers,
Zoltán
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03389 seconds