Scala plugin almost useless - is it just us?

This is getting extremely frustrating.
We are getting continual deadlock-freezes in Intellij when editing our scala files - as documented in http://youtrack.jetbrains.net/issue/SCL-2753
This issue is flagged as "critical" but doesn't seem to have moved for weeks.

We had some ability to work by reverting to Idea 10.0.0.1 but it's still not completely stable - and after trying to do a big refactor yesterday found that now our project is uneditable in both 10.0.0.2 *and* 10.0.0.1 - and I just tried the latest EAP and latest nightly build of the Scala plugin, and it still doesn't help.

I'm trying to work out - why is this issue plagueing us so badly, but (from the complete silence on this forum) not other people?  Is it something about the libraries we are using?  We're using the lift-mongodb driver, which I'm in the process of trying to replace with the Casbah mongo driver - both of these do a chunk of metaprogramming, is it possible one of them is causing the IDE such pain?

Any thoughts?  Anyone else struggling with this issue? I'm about to start trying other IDEs, just to get us working again - which is frustrating, especially as we managed to get Intellij licenses for our project on the basis of it's great Scala support!

- Korny

5 comments
Comment actions Permalink

Of course, having whinged about this, I proceeded to find what looks like a solution - or at least a workaround... :)
We were running with two Scala libraries - one using Scala 2.7.7 for our sbt build, and one using Scala 2.8.1 for our app.
Even though none of the code we were editing should have been using the Scala 2.7.7 compiler, it seems that removing that library entirely has made things rather more stable.
Hopefully it will stay stable!

0
Comment actions Permalink

The latest nightly build (http://confluence.jetbrains.net/display/SCA/Scala+Plugin+Nightly+Builds+for+IDEA+X) possibly contains fix for this deadlock. Please try it and report me back if it's ok or not.

Best regards,
Alexander Podkhalyuzin.

0
Comment actions Permalink

Hi - sorry to say, it doesn't help - if I re-enable scala 2.7.7 on our project, it starts freezing again, even with the latest EAP and the latest nightly build.

0
Comment actions Permalink

In a way that is good news: it seems to confirm that having difference scala versions attached to different modules triggers the problem.

0
Comment actions Permalink

There is also interference if different Scala versions are attached to different projects, opened simultaneously.

See http://youtrack.jetbrains.net/issue/SCL-2813
The attached minimal test case is reproducible for me using latest nightly builds.

-tt

0

Please sign in to leave a comment.