Closed brice-morin closed 5 years ago
Seems like XText does not work with OpenJDK 11 (eclipse/xtext#1316), which was the base image for the official maven image. Trying to downgrade to OpenJDK 10 (which does not seem to be a popular version... but it should be good enough for now for us)
Oh yes, using Docker base images without specific version numbers has made me desperate more than once in the last few months.
Failed also with OpenJDK 10 and 8. It seems there is another issue with XText: eclipse/xtext#1373
@ffleurey Seems like we need to upgrade XText :-)
I am fine with it because now the new version is by default in the Eclipse distrib 😊
Franck
Provenance : Courrier pour Windows 10
De : Brice Morin Envoyé le :mercredi 6 février 2019 15:46 À : TelluIoT/ThingML Cc : Franck Fleurey; Mention Objet :Re: [TelluIoT/ThingML] ThingML does not compile on MacOS or insideDocker (#278)
Failed also with OpenJDK 10 and 8. It seems there is another issue with XText: eclipse/xtext#1373 @ffleurey Seems like we need to upgrade XText :-) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Well, I could give it a try this week, but I remember that task was not as simple as it should be (quite a few places where the version needs to be updated).... But I am very happy if anyone else volunteers :-)
Well, that is a pain to migrate to Xtext 2.16 (the one integrated in Eclipse 2018-12). I now have to workaround that issue eclipse/xtext#1231
Now fighting with eclipse/xtext-xtend#576
Seems like the painful update to Xtext 2.16 helped. At least I was able to build and run ThingML within Docker.
Well, it seems there is still some problems compiling ThingML on MacOS... but the Docker image has successfully been tested on MacOS, providing an OK work-around :-)
@nicolasferry cannot compile ThingML on this Mac... :-)
To help him, since he's obviously not helped by his machine, I decided to make a Docker image, which basically clones the ThingML repo, compiles it, and somehow exposes the all-in-one jar. Well... it turns out I have the very same problem like he has (see below). Strangely, on a proper Linux machine, I am able to compile...