-
Notifications
You must be signed in to change notification settings - Fork 17
errors after importing project #533
Comments
It looks like you had no JDK configured for this project, otherwise there's no reason that stuff from java.lang couldn't be found. I'm going to add a big red warning for Ceylon projects that should be compiled for the JVM but have no JDK attached. |
i.e. Diego's project configuration uses |
Alright, fine, but it's never OK that compilers crash out with weird stack traces! That's not how we report errors to users. Not ever. |
I'm pretty sure these errors could also be found in Eclipse's log. The problem here is that IntelliJ sees those errors and shows them in the UI. |
We now have a notification telling users when a JVM project has no associated JDK. It's shown during full builds (when the project is opened and when Reset Ceylon Model is called). |
I got lots of these after importing @DiegoCoronel's Swarm example project. I've also seen it recently in other circumstances.
The actual stack trace is:
The text was updated successfully, but these errors were encountered: