Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems to create a target platform with Xtext and Buildship #1529

Closed
UdoW opened this issue Aug 5, 2019 · 13 comments
Closed

Problems to create a target platform with Xtext and Buildship #1529

UdoW opened this issue Aug 5, 2019 · 13 comments
Labels
Milestone

Comments

@UdoW
Copy link

UdoW commented Aug 5, 2019

I try to create a target platform for a runtime Eclipse RCP application where I want to use Xtext 2.18.0 and Buildship 3.1.1 based on Eclipse 2019-06.

Xtext needs Guava 21.0.0 and Buildship needs Guava 27.1.0.

In the Xtext Orbit p2 repository I can find the Guava 27.1.0 version but some Xtext bundles still require Guava 21.0.0.

How can I bundle both?

Is there a general plan which version of a "common" bundle to use for each platform release?

E.g. Guava 27.1.0 on Eclipse 2019-06, Guava 21.0.0 on Eclipse 2019-03 etc.

@cdietrich
Copy link
Member

cdietrich commented Aug 5, 2019

@cdietrich
Copy link
Member

cdietrich commented Aug 5, 2019

=> the buildship you use seems too new.
which buildship do you use consumed from where
=> maybe you should use buildship 3.0.0 or 3.1.0

@UdoW
Copy link
Author

UdoW commented Aug 5, 2019

I consumed version 3.1.1 from this repository:
https://download.eclipse.org/buildship/updates/e411/releases/3.x

As I thought that is is compatible with Eclipse 4.11 (2019-03) and Xtext 2.18.0 ist also compatible with Eclipse 4.11 both should match.

Do you know if there is an agreement of all feature contributors to an Eclipse Release version which external bundle version to use? Otherwise this will be a mess of conflicting versions forever.

@cdietrich
Copy link
Member

there is just a loose agreement.
my assumption is that with eclipse 2019-09 everybody will be at guava 27.1

@cdietrich
Copy link
Member

(you may address this issue by writing your concerns to https://accounts.eclipse.org/mailing-list/cross-project-issues-dev

@cdietrich cdietrich added this to the Release_2.19 milestone Aug 5, 2019
@cdietrich cdietrich changed the title Problems to create a target platform with Xtext and Buildshipp Problems to create a target platform with Xtext and Buildship Aug 5, 2019
@UdoW
Copy link
Author

UdoW commented Aug 5, 2019

ok, thank you.

@cdietrich
Copy link
Member

@UdoW are you going to write to cross project issues dev or shall i do?

@UdoW
Copy link
Author

UdoW commented Aug 5, 2019

I wrote some questions.

I also found out that Buildship 3.1.0 depends on Guava 21.0.0 but version 3.1.1 depends on 27.1.0. I think this is a regression.

@cdietrich
Copy link
Member

cdietrich commented Aug 5, 2019

no its a feature
xtext 2.19 and mwe 2.11 use guava 27.1 too.
the problem is that you try to use buildship 3.1.1 with old stuff

@UdoW
Copy link
Author

UdoW commented Aug 5, 2019

But then I do not understand the concept of semantic versioning.
I downgraded to Buildship 3.1.0 and now it works together with Xtext 2.18.0.

@cdietrich
Copy link
Member

well the problem is: all using the same guava version is not part of the semantic versioning.
i dont think buildship has any public api so semantic versioning is irrelevant there

@UdoW
Copy link
Author

UdoW commented Aug 5, 2019

Buildship has some public API since version 3.0.0, but nevermind.

@miklossy
Copy link
Contributor

miklossy commented Aug 5, 2019

I observed a similar problem on the Eclipse GEF project, see bug 549806

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants