Scala plugin EAP for IntelliJ IDEA 14 EAP is Out

New IntelliJ IDEA 14 EAP is already available, and we just released the new Scala plugin for it. You can get the latest update via Settings → Plugins.

Here’s a brief overview of what’s new in this version:

  • Parameter info for infix method calls
  • Java to Scala converter fixes
  • Error highlighting fixes
  • Type variable in patterns support
  • Performance improvements for big “for expressions”
  • New inspection: explicit type for implicit functions
  • New inspection: detect useless expressions
  • Change signature for constructors


For the complete list of changes, refer to the Release Notes.

As always, you’re welcome to share your feedback in our discussion forum or issue tracker.

Develop with Pleasure!

This entry was posted in Uncategorized and tagged , . Bookmark the permalink.

8 Responses to Scala plugin EAP for IntelliJ IDEA 14 EAP is Out

  1. kerr says:

    thanks for all your hard works

  2. Jon Wu says:

    Thanks so much for fixing bogus errors!

  3. Michael Li says:

    Still no working for Slick Group By grammar, for instance:
    we had the aggregations on multiple fields, but for the last map function, the field names after wildcard letter “_”, not recoganized.
    implicit session =>
    val spQuery = Storeperf.filter(sp => sp.opendate === sqlOpenDate)
    storePerfList = spQuery.list
    spTotal = spQuery.groupBy(sp => sp.opendate)
    case (opendate, group: Query[Storeperf, StoreperfRow, Seq]) => (group.length,,,

  4. David Perez says:

    Is the new support for SBT + android-sdk-plugin + Android already integrated?

  5. Javawerks says:

    SBT ( import ) support is still broken by this bug:

  6. Sergii says:

    I have a general question related to this way of organization of project:

    If for example I have a Python plugin installed and a python-based module then to confiugure the project I need to add a Python SDK in the Platform Settings -> SDKs section of the project configuration. After this the Python interpreter library is automatically added to global libraries. Thus the question is: why did you decide to add the scala-sdk directly to global libraries instead of adding it to SDKs which would be logical regarding naming and moreover this apporach would be consistent with other language plugins?

Leave a Reply

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