Hi, Ernesto,
That quotation looks to me like the Xtext plan is to test for API compatibility and increase their dependency bounds to include version 21. But, at any rate, the question of aligning every project on version 21 is still up in the air, going back to the Architecture Council for review, so we may still be dealing with deployment of multiple versions.
At any rate, I have no objection to doing what is necessary for us to continue linking correctly to Papyrus and to Xtext. AFAIK, our usage of Guava is only in the most stable of their APIs, but it seems that even something like their Futures is seeing breaking changes these days, so who knows? I think we should at least make an effort not to expose Guava types in our APIs to ensure that we don’t add to the OSGi wiring problems.
On May 8, 2017, 15:35 -0400, Ernesto Posse <eposse@xxxxxxxxxxxxx>, wrote:
I just got a response from the Xtext people about 2.12, in particular if they are going to move the dependency to Guava 21 and the response was:
> we are still discussing on this.
> likely we stay as we are and inc the max version to 21
That means that we might need to include a dependency to an older version of Guava (i.e. 18), otherwise the Codegen bundles won't be resolved.
I've prepared a couple of gerrits to add Guava 18 explicitly: the TPs and MANIFESTs (
96604) and the Oomph setup (
96605). Are there any objections to merging them?
--
Ernesto Posse
Zeligsoft
Since projects are moving to Guava 21 and apparently we need Guava 18 to deal with
Bug 516200, would there be any objections if I make the Guava dependency for codegen to be [18.0.0,22.0.0)?
--
Ernesto Posse
Zeligsoft
As far as I'm concerned we don't need Xtext 2.12. Remi updated the MANIFEST files to use
org.eclipse.xtend.lib;bundle-version="[2.12.0,3.0.0)",
org.eclipse.xtext.xbase.lib;bundle-version="[2.12.0,3.0.0)"
(although I thing he missed some).
I'm not sure why. I suspect it was because Xtext 2.12 is supposed to be released with Oxygen.
But it looks like Xtext 2.12 is actually causing some trouble. See
Bug 516200.
--
Ernesto Posse
Zeligsoft
Thanks, Peter.
I’ve updated the Gerrit.
Cheers,
Christian
On May 8, 2017, 08:05 -0400, Peter Cigéhn <
peter.cigehn@xxxxxxxxx>, wrote:
Hi,
Regarding Xtext 2.12 it seem that it will be included in Oxygen M7:
So I guess until then we need to add the Xtext p2 repo ourselves to the Tester Setup. Found the following p2 repo based on the changes in the referenced Gerrit change in the message linked above.
I made an update to my local version of the Tester Setup model file and was able to install Papyrus-RT Oxygen with no additional issues.
/Peter Cigéhn
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
--
--
--
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev