Build compiler crash should be handled gracefully
When the SBT build compiler crashes because of a Scalac crash, the failure should be handled gracefully.
For instance, the attached zip contains a Scala project that produces a compiler crash (*only in 2.10.0*) when you edit the BugTest souce (for some reason it doesn't always crashes. But, if try hard enough, you should see it). The compiler crashes with a StackOverflowException, and because we don't handle the exception the user gets two annoying dialogs displayed. The first one, is an error dialog reporting the StackOverflow error, the second one is an Eclipse dialog saying that an uncaught exception was intercepted by the workbench and that you should quit Eclipe.
The fix would be to provide a single dialog that explains what happens and suggest to open a ticket in the Scala issue tracker.
For instance, the attached zip contains a Scala project that produces a compiler crash (*only in 2.10.0*) when you edit the BugTest souce (for some reason it doesn't always crashes. But, if try hard enough, you should see it). The compiler crashes with a StackOverflowException, and because we don't handle the exception the user gets two annoying dialogs displayed. The first one, is an error dialog reporting the StackOverflow error, the second one is an Eclipse dialog saying that an uncaught exception was intercepted by the workbench and that you should quit Eclipe.
The fix would be to provide a single dialog that explains what happens and suggest to open a ticket in the Scala issue tracker.
Leave a comment
file:afeKDKziSr4QmyacwqjQWU
project sample
project sample
on 2015-03-27 15:52 *
By Simon Schäfer
Eclipse version changed from Helios - Eclipse 3.6 to Luna - Eclipse 4.4
Version changed from 2.1.0-M3-210 to 4.0.0
Milestone changed from Helium SR1 to -none-