-
Notifications
You must be signed in to change notification settings - Fork 28
Intermittent "Initializing Java Tooling" error on launch #1866
Comments
Same on "Oxygen Release (4.7.0)" w/Ceylon 1.3.2 |
Stack trace from a fresh install:
|
Confirmed: I just started seeing this error after upgrading to Oxygen. |
I can make that error go away, but then I just get this one instead:
So it looks like we have a major problem with the metamodel not being set up. @davidfestal @FroMage I'm going to need your help here:
|
It seems to be a race condition that could sometimes happen in previous Eclipse versions, but now happens systematically under Oxygen when starting Eclipse with a Ceylon project opened. The Ceylon meta-model is registered in a Job, and it happens that, now, the Ceylon classpath-container initializer of a project is indirectly called by the JDT initialization before the end of Ceylon meta-model registration. And some Ceylon classes are involved in the implementation of the Classpath-container initializer. I'll try to provide a fix for this asap. |
Thanks David. |
This is not intermittent for me but happens every single time I launch/restart Eclipse on Linux and macOS. |
Right, me too. |
This is fixed, but at the cost of unnecessary binary builds on almost every startup. We need to come back and fix that. |
See #1882. |
After updating to 1.3.2, on rare occasion, when launching launching Eclipse, with a Ceylon project already open from a previous session, I've encountered...

Windows 10, JDK 8 u121, Eclipse Mars 4.5.2
The text was updated successfully, but these errors were encountered: