no scala library recognized after update to newest eap build? Follow
symptom: all scala library files in my editor are red even though the project configuration seems to be correct.
i tried to go back to an older version - but even with the official releases 14.0.2 & 1.2.1, the problem persisted. reimporting my sbt project didn't change anything, invalidaing caches didn't change anything.
what are the things i should try to get it working again?
Please sign in to leave a comment.
I had this problem with existing .idea projects. I found that deleting .idea and .idea_modules and importing the sbt-based project directory anew solved this. You have to be patient until the whole import process has finished (background task). I also remember having had problems when switching from 1.2 to 1.2.1, where I needed to switch the JDK version forward and backward if I didn't want to wipe the .idea folder.
I hope that helps. Best, .h.h.
When you get symptoms like these, especially after a version update, the
cache is often the problem. On the Mac, under the File menu, there's an
option to invalidate the caches and restart.
On 1/7/15 12:51 PM, Dennis Haupt wrote:
Thanks! I had the same problem and clearing the caches worked for me. I rarely have to do it so I forget.. :)
I've had to do the cache invalidation thing three times today. For some reason it just forgets about my Scala. Modules still have scala-library as a dependency.
I am upgraded to version 220.127.116.11.EAP of the plugin, IU-139.872.1 of Intellij today. I am using Maven (not sbt).
I ended up switching back to 14.0.2. I had to blow away my .idea and .iml and invalidate the cache.
I finally found problem in JIT when b & 0xFF calculates to b after JIT. I replaced it by appropriate if/else (by sign of b) and reproducible example I had became ok.
So you can try scalap.jar from issue, which I attached earlier, or just wait for the next update, when I'll finally release it.
Thanks! I'll check the next one.