Aladdin - Scala Bugtracking
[#437] project: eclipse-plugin priority: high category: bug
submitter assigned to status date submitted
Gilles Philippe won't fix 2005-05-31 14:07:25.0
subject Eclipse enters coma when scalac raises an exception
code
No specific code, but a corrupted scala home directory (rename lib to lib1) or a version of scala that fails when compiling.
what happened

When compilation fails with an exception, no error message is generated and Eclipse silently stops compiling \ any Scala file.

Worse, when Eclipse is freshly started and one file in any scala project fails to compile, all Scala tools, i\ ncluding the editor stop working (Opening an editor give the following, rather unhelpfull, message: "Unable to c\ reate this part due to an internal error. Reason for the failure: Editor could not be initialized.")

Even worse, the Scala preference pane itself dies a painful death ("An error has occurred when creat\ ing this preference page.") that prevents one to revert to a working Scala root directory.

Of course, the error log fills with "Unexpected exceptions", but no usefull error message is forwarded to the\ user. It also isn't possible to know which file was being compiled when this "Unexpected exception" was thrown.\

what expected
  • A message identifying the exception and saying wich file's compilation causes it.
  • The possibility for the editor and the preference pane to continue working even when the Scala compiler isn't.
[back to overview]
Changes of this bug report
Gilles  edited on  2005-06-13 10:34:39.0
Added "even worse" comment about the dying preference pane.
Gilles  edited on  2005-06-13 10:36:07.0
Gilles  edited on  2005-06-13 10:40:15.0
Raised priority to high. In particular, it is necessary for the file where the compilation exception happened to be referenced.
Gilles  edited on  2006-03-24 17:35:30.0
Refers to old eclipse plugin.