-
-
Notifications
You must be signed in to change notification settings - Fork 428
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
Upgrade Xtext to 2.17 for full Java 11 support #650
Conversation
08c8da4
to
7c36fda
Compare
Upgrading the p2-maven-plugin to 1.3.0 fixed that new Java 11 error. There seem to be some tests failing on Java 11 now. It looks precision related:
When building openhab2-addons using a local build of openhab-core and this PR there's an error where the build cannot find the new artifacts:
That is to be expected I think because they need to be added to a new openhab-deps-repo version? Is there an easy way to workaround this and test if all works well? |
You could use the runtime BOM as a dependency then everything should be able to resolved by the POM considered dependencies. But it will slow down the whole build. |
I managed to get my own p2 repo using Eclipse 2019-03 deployed which I could use for creating a working distro. The distro started and the demo didn't show any issues. :-) For creating the p2 repo the changes in openhab/openhab-deps-repo#12 are required. The bundle list reported by Karaf is available in this bundle-list.txt. |
Signed-off-by: Wouter Born <[email protected]>
Signed-off-by: Wouter Born <[email protected]>
Signed-off-by: Wouter Born <[email protected]>
7d41142
to
fbd4ab6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
@@ -42,7 +42,7 @@ | |||
<groovy.eclipse.compiler.version>2.9.2-01</groovy.eclipse.compiler.version> | |||
<groovy.eclipse.batch.version>2.4.3-01</groovy.eclipse.batch.version> | |||
|
|||
<ohdr.version>1.0.40</ohdr.version> | |||
<ohdr.version>1.0.41</ohdr.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will merge as soon as @kaikreuzer informs us that ohdr 1.0.41 is published.
I assume I can wait for a notification that the respective pull request you created is merged.
Is it enough to wait for a new build of https://ci.openhab.org/job/openHAB-Deps-Repo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's right! I studied how it all works for creating my own P2 repo. ;-) As a sanity check you can also check that the new version is available at the OH P2 bintray repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It has automatically been published by running https://ci.openhab.org/job/openHAB-Deps-Repo/48/.
* Upgrade Xtext to 2.17 for full Java 11 support Signed-off-by: Wouter Born <[email protected]> GitOrigin-RevId: 2c7ca34
This is a PR to upgrade Xtext to 2.17 (#646). The PR already builds successfully on Java 8 and on Java 11 it now builds 105/127 projects. :-)
I haven't tested the end result yet but maybe you can see if all the upgraded dependencies/features make some sense @maggu2810 / @kaikreuzer?
The Java 11 build now fails with:
[ERROR] Failed to execute goal org.reficio:p2-maven-plugin:1.2.0:site (default-cli) on project org.openhab.core.features.p2.repo: Execution default-cli of goal org.reficio:p2-maven-plugin:1.2.0:site failed: org.apache.maven.plugin.MojoExecutionException: Unable to execute mojo: P2 publisher return code was 13 -> [Help 1]
Fixes #646