IntelliJ IDEA 2016.3.1 is Out

If you haven’t tried the new and shiny IntelliJ IDEA 2016.3 yet, there’s a good reason to do it right now. Welcome IntelliJ IDEA 2016.3.1, an update that brings lots of important bugfixes.

One of the most notable changes in this build is the long-awaited support for JUnit 5 M3, so if you plan to keep running JUnit 5 M2, you have to either use IntelliJ IDEA 2016.3 (or earlier), or manually include JUnit 5 M2 dependencies in your classpath (junit-platform-launcherjunit-platform-commons, junit-platform-engine; junit-jupiter-api and junit-jupiter-engine for Jupiter; and junit-vintage-engine for Vintage).

Speaking of JDK 9, IntelliJ IDEA 2016.3 won’t support builds 148 and up because they contain code that breaks things. Of course, we’re working to resolve this, and will support the latest JDK 9 builds in 2017.1 (its EAP may well start within the next few weeks).

In other news:

  • Move Element Right/Left actions are now available for Groovy
  • WebSphere support has been updated to v9

For the complete list of changes in this update, see the release notes.

Develop with Pleasure!

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

7 Responses to IntelliJ IDEA 2016.3.1 is Out

  1. Baron Roberts says:

    Congrats on the release. Can you upload 2016.3.1 to so that the Jetbrains’ gradle-intellij-plugin can download it. Thanks!

  2. Anton says:

    I think “What’s new” button in the IDE popup should send to the Release Notes ( and not to this page: (which is the feature overview for the latest version of IntelliJ, I assume).

  3. Ian Bogste says:

    When you mentioned JFK 9 non-support above, does that mean that Jigsaw is supported in pre-148 builds? Because I was looking for quite some time for Jigsaw support in IntelliJ and had to resort in Maven CLI and other hacks to “make it work”.

  4. K Nair says:

    Any idea why alt+enter is not suggesting me introduce new local variable? Anybody else having same issue?

  5. David Mabe says:

    This upgrade has removed grails 3 support from my project with no clear path to add it back.

Leave a Reply to Baron Roberts Cancel reply

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