What to Check Out in Scala Plugin 1.4.x for IntelliJ IDEA 14 & 14.1

If you’ve already upgraded to IntelliJ IDEA 14.1 (released just a few days ago), you might’ve noticed (in addition to all of its awesome new features), a new Scala plugin update: v1.4.15.

The update brings you quite a few improvements for the Play framework support: fixed problems with running of the applications, and better yet, JavaScript injection to Play templates. 1.4.15 is the first of the planned series of Scala plugin updates that will be available exclusively for IntelliJ IDEA 14.1, because at this moment IntelliJ IDEA 14 only receives bug fixes, whereas the new feature development is entirely focused on 14.1. This also means more new features and improvements are on the way for it, so getting the 14.1 is a good idea (if you haven’t done this already.)

Now that I’ve already got your attention, I’d also like to review what’s exactly new in this Scala plugin version (in case you haven’t followed the EAP news.)

Advanced Implicits Analyser

One of the major new features is, of course, the advanced implicits analysis. Now when you call the Implicit Parameters action, in addition to the list of applicable implicit parameters, you will see those that can’t be found:

Screen Shot 2015-03-02 at 20.20.51

Under the “Parameter not found” label you’ll find the list of possible implicits for this location. It distinguishes the following cases:

  • Fewer applicable implicits are found
  • Somewhere deep an implicit is not found or diverging
  • No applicable implicits found for this parameter

Compiler Server for Play Framework

Another improvement is aimed at making the compilation for Play applications blazingly fast, thanks to moving it to a separate process. Now every time we compile the project we don’t have to start SBT.

Activator Templates

One more enhancement is the newly-added integration with Typesafe Activator that helps you create new projects based on the Activator templates from inside the IDE’s Project Wizard:


An SBT Plugin for Tweaking IDE Settings

Finally it’s worth mentioning that we’ve introduced the support of our sbt-ide-settings plugin, which provides additional settings that improve importing, compilation and testing of SBT projects.

For example, the ideExcludedDirectories option lets you instruct IntelliJ IDEA which directories to exclude on project import.

Another option is ideBasePackages, which configures a list of packages to be used as base prefixes for chaining. The packages beginning with one of these prefixes will be chained automatically in IntelliJ IDEA.

That’s pretty much it, you’re welcome to discover other enhancements by updating to the newest Scala plugin yourself.

UPDATE: If you’re experiencing problems with installing of the update, we recommend you to uninstall the previous version and than install the latest version from the scratch. Alternatively, you can download and install the plugin manually. We’re working on fixing the problem as soon as possible.

As always we’re open to your feedback: don’t forget to write us in the discussion forum and the issue tracker.

Develop with Pleasure!

About Andrey Cheptsov

Part-time dreamer. JVM/JavaScript geek. IntelliJIDEA Marketing Manager at JetBrains.
This entry was posted in Uncategorized and tagged , , , , . Bookmark the permalink.

38 Responses to What to Check Out in Scala Plugin 1.4.x for IntelliJ IDEA 14 & 14.1

  1. James says:

    I can’t get this to install. I updated to IntelliJ 14.1 CE which requests the update, but after downloading the plugin it does not seem to install it.

  2. Ivan says:

    I’m facing the same issue as James – IDEA downloads the Scala plugin update but does not install it. I use 14.1 Ultimate Edition.

  3. Ondrej says:

    It is quite ironic for me to read this blog, as the update is annoyingly hard to install – see https://youtrack.jetbrains.com/issue/IDEA-138220

  4. Arun says:

    I ran into similar problems with IntelliJ 14.1 CE. The Scala plugin would not install and it kept bugging me to install the plugin. My Scala/SBT projects would not be recognized. I finally gave up and went back to the prior version. I notified all my fellow developers to hold off on upgrading to IntelliJ 14.1 CE until a new version is available. I hope that will be soon.

  5. Sergey says:

    I want Haskell support :)

  6. Andrey says:

    Scala console is now broken: [Cmd] + [Enter] does not execute the code

  7. Wayne Wang says:

    Play launching problem still exists under multi-modules projects.

    Now it runs every time but stop at the error of :
    [warn] No main class detected

    java.lang.RuntimeException: No main class detected.
    at scala.sys.package$.error(package.scala:27)

    And this happened under my multi-modules project which I have copied the structure from play-akka-cluster-example from activator templates

  8. Ricki says:

    For some reason my Play Framework 1 projects have issues with IntelliJ IDEA 14.1. Not sure if it is the scala plugin, or 14.1 itself, but my Play Framework 1.2.7 project keeps reindexing all the files all the time, so I have to revert back to 14.0.

    Anyone else had this issue or have a clue how to resolve it?

  9. Ahti says:

    How fast should be blazingly fast?

    With the empty java play 2 project created with the new project wizard I still get ~8sec delay before every test run (Make process, possibly SBT build).

    Even after “Start Watcher” SBT Make still seems to kick in and I don’t see anywhere SBT server kicking in. Is this how it should work or something MUST be wrong with my settings? I tried to doublecheck every single thing.

    This is fresh 14.1 IDEA with Scala plugin 1.4.15.

  10. Sergey says:

    Thanks for “moving it to a separate process” & sbt !

  11. Golly says:

    […] list of packages to be used as base prefixes for chaining. The packages beginning with one of these prefixes will be chained automatically in IntelliJ IDEA.

    What does this mean? Could you explain what you mean by chaining? Thanks.

  12. David Pérez says:

    I don’t understand the “ideBasePackages” setting.
    Could you please provide an example?

  13. Dmitry says:

    Finally my inline JS is highlighted correctly! :)
    Thanks for the great work guys!

  14. Why can’t I add command line arguments to the Play 2 launch configs? I need to run activator commands like “start 80” or ‘h2-browser “run 9000″‘ but the plugin won’t let me do that. So I have to use a hack based on the Bash plugin to launch my Play applications from the IDE.

  15. Ercan says:

    After install intellij idea 14.1.1 update my mac osx lost stability. Now i have Lots of noise when intellij open. Another error is Gauge plugin related. Not working correctly.

  16. antonkulaga says:

    The plugin is really buggy, it does not compile most of more or less complex projects and it even cannot import projects like https://github.com/w3c/banana-rdf

  17. Sam Yang says:

    I have 14.1.1. I can’t create play 2.x project by combining the Scala/Activator templates.

    Any recommendation?

  18. HamsterofDeath says:

    can the implicits analyzer show the implict parameters applied to an implicit conversion method? if yes, how? if not, i would like that to be possible.
    can’t read my own code otherwise :)

  19. Jonathan says:

    Since updating to the latest IntelliJ14.1.1 and latest scala plugin, my scala facets and play project are broken in that I had to delete my .idea directory, and it still doesn’t recognize that it is a play project on fresh import via sbt, although I get syntax highlighting, method completion, etc., but the project settings don’t see play/scala facets, etc., and debugging config is broken. This is a real drag. :(

    Although I am happy with the pace of features, quality and clean upgrade support need much more attention and investment.

  20. Jonathan says:

    Just tried to grab the bleeding edge 1.5 scala plugin version from: https://confluence.jetbrains.com/display/SCA/Scala+plugin+EAP in faint hope to fix the facet issue, and am seeing:

    This XML file does not appear to have any style information associated with it. The document tree is shown below.

    Access Denied



  21. Alex says:

    I installed plugin 1.4.15 on 2 different Mac’s and having same problem.

    Activator 1.3.2 (latest play framework)
    IDEA 14.1.2 CE
    Scala plugin 1.4.15

    When I create a new Scala/Activator project , a popup appears “New Module: Error adding module to project: null”

    Logs show the following:
    WARN – il.projectWizard.ModuleBuilder – -1

    Any ideas? Thanks

  22. Peter Tobler says:

    I’ve seen lot of posts that people cannot create Play projects. I’ve had the same problem until now and I’m glad I found a fix for it. Just delete your config folder(s) according to https://intellij-support.jetbrains.com/entries/23358108-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs

    Next time I’ll definitely do a clean install, even for minor updates.

  23. Heming says:

    The SBT project with multiple sub-projects is not recognized correctly. 14.1.2 worked fine though.

  24. angel says:

    Hi!..I’m having a little trouble with my intellij…seems than sbt and intellij are using different ivy locations because when I update my deps with sbt and then open the project with scala, all the deps are re downloaded again, the same happens in the inverse order, I’ve changed my sbt-launcher.jar ubication and now sbt and intellij are using the same tool, but the problem persist, how can I configure the ivy location for intellij?..thank so much

  25. Newton says:

    Keep this goin please, great job!

    Here iss my web-site; tungsten carbide engagement
    rings (Newton)

  26. Dev says:

    Error:scalac:Parameter ‘-nobootcp’ is not recognised by Scalac
    Error:scalac:bad option:’-nobootcp’
    how to git rid of this please ?

  27. I’m gone to say to my little brother, that he shoul also go to see this website on regular
    basis to take updated from most up-to-date gossip.

Leave a Reply

Your email address will not be published. Required fields are marked *