New release candidate for Scala IDE for Eclipse 2.0.1
A quick lick of paint for Scala’s Eclipse IDE
Rolling on from their big Typesafe stack announcement recently, there’s been further progress made on the road towards Scala IDE for Eclipse 2.0.1, with the reveal of the first release candidate.
Codenamed Helium, Typesafe’s Scala IDE for Eclipse aims to truly give the growing Scala community a first-class IDE they crave – featuring a Scala editor with syntax highlighting, code completion, inferred type hovers, hyperlinking to definitions, error markers and much more. There’s still that underlying recognition that Java and Scala need to support each other and what better way of getting that than using the most popular Java IDE as a template.
Although primarily a maintenance release for the Scala IDE released at the back end of last year, 2.0.1 RC1 improves the link between sbt and the builder further by ‘following sbt more closely when dealing with dependent projects‘. So, when a project has build errors, dependent projects are not rebuilt and the Eclipse builder compiles exactly the same amount of files as the command line.
Other than that, it’s a bit of polishing up. Niggling editor
issues have been fixed, such as double braces being
inserted and deleted together, completions that need an additional
import won’t mess up the file, and
Declaration works when called from the contextual
menu. You can expect a better compiler too, with small tweaks being
made to make it able to deal with multiple compiler plugins
alongside each other.
Finally, this version works with both Eclipse 3.6 (Helios) and 3.7 (Indigo). The team have developed and tested it using Java 6, but say Java 7 can be used with some caveats. All good stuff, I’m sure you’ll agree.
Although perhaps slightly behind, the Scala IDE roadmap reveals what else will be in Milestone 1. And there’s a lot of work to be done as you would expect with something this huge:
It is recommended that users update as soon as possible to this version, which you download here. For now anyway, the team tell us ‘to go forth and code’. We shall indeed.