[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [incquery-dev] Xtext 2.6 dependency
|
Hi,
the problem is, if the language infrastructure is generated with Xtext 2.5, it only works with 2.5 and the same goes for the generated infrastructure with 2.6. In the current version compile errors and classdefnotfound exceptions are thrown if I would try to add an [2.5, 2.7) interval.
In other words: we could use the same code base to work with _either_ 2.5 or 2.6, but not both, and that will be represented by the strict dependency.
Cheers,
Zoli
-- Zoltán Ujhelyi
https://www.inf.mit.bme.hu/en/members/ujhelyiz
Fault Tolerant Systems Research Group
Budapest University of Technology and Economics
On 2014.06.23., at 11:25, Bergmann Gábor <bergmann@xxxxxxxxxx> wrote:
> Hi,
>
> I do not understand, even after re-reading your message.
>
> If you have found "our code base compatible with both 2.5 and 2.6", why is it that the newer change "sets the required dependency to 2.6", so that "our tooling will have a strict dependency to Xtext 2.6"?
> Did you mean to say that the Gerrit change "declares additional compatibility with 2.6" as opposed to strictly requiring it? Because that would make more sense given your findings. And a version interval of [2.5.something, 2.7) is indeed what I have found by randomly sampling a MANIFEST.MF change in review, so maybe this was your intention all along :)
>
> Or is there any actual restriction / incompatibility that is newly introduced?
>
> Cheers,
> Gábor
>
> -----Original Message----- From: Ujhelyi Zoltán
> Sent: Monday, June 23, 2014 10:08 AM
> To: Incquery developer discussions
> Subject: [incquery-dev] Xtext 2.6 dependency
>
> Hi all,
>
> as we are getting used to it, Xbase has changed in Xtext 2.6 (again) in a way, that is not compatible with IncQuery built with 2.5. During the weekend, I have tested Xtext 2.5/2.6 compatibility, and removed some deprecated stuff (in http://git.eclipse.org/c/incquery/org.eclipse.incquery.git/commit/?id=245d6c8ccd7dff76f5e38f04f7866f040e6ecba5), making our code base compatible with both 2.5 and 2.6 (but possibly breaking Xtext 2.4, if that will be required in the future).
>
> Additionally, I have a code review waiting for inclusion that sets the required dependency to 2.6 (https://git.eclipse.org/r/#/c/28847/), if nobody objects, I will merge it today (and after that, our tooling will have a strict dependency to Xtext 2.6 - the runtime is Xtext-independent of course).
>
> Cheers,
> Zoli
> -- Zoltán Ujhelyi
> https://www.inf.mit.bme.hu/en/members/ujhelyiz
>
> Fault Tolerant Systems Research Group
> Budapest University of Technology and Economics
>
> _______________________________________________
> incquery-dev mailing list
> incquery-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/incquery-dev
>
>
> _______________________________________________
> incquery-dev mailing list
> incquery-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/incquery-dev
