Opening a Scala file in Java project tries to use the presentation compiler (and fails)
The Scala editor wants to open any file with a .scala extension, regardless of its project type. If the project doesn't have the Scala library on its classpath, this of course means that the presentation compiler will fail to initialize and the user will get an error message.
The correct behavior is that the presentation compiler should not be initialized for such projects. This may require re-architecting the Scala editor hooks.
The correct behavior is that the presentation compiler should not be initialized for such projects. This may require re-architecting the Scala editor hooks.
Leave a comment
on 2011-03-25 09:11 *
By Iulian Dragos
Version set to 1.0.0-SNAPSHOT
Eclipse version set to Helios
Branch set to wip_experiment (2.9)
Updating tickets (#1000238, #1000326, #1000331, #1000264, #1000298, #1000314, #1000315, #1000325, #1000329, #1000333, #1000277, #1000209, #1000210, #1000288, #1000299, #1000300, #1000301, #1000305, #1000309, #1000310, #1000327, #1000270, #1000292, #1000293, #1000294, #1000295, #1000297, #1000303, #1000304, #1000312, #1000320)
on 2012-01-27 14:20 *
By skyluc
Type set to Defect
Version changed from 2.0.0-beta1 to 2.0.0-final-29
Eclipse version changed from Helios to All
Assigned to changed from lindydonna to -none-
Component changed from None to Editor
Milestone changed from Helium to Backlog
Permission type changed from None to Public
Status changed from New to Accepted
Seems to be fixed. Can't reproduce anymore.