IntelliJ IDEA 2017.1: Java 9, Kotlin 1.1, Spring, Gradle, JavaScript, Go and more

IntelliJ IDEA 2017.1 is available for download! In addition to many important bug fixes, this massive update brings lots of improvements to supported languages, frameworks, and built-in tools.

  • Java 9: The latest builds of JDK 9 are fully supported, with assisted project import and coding assistance for editing module declarations. Built-in inspections validate module declarations and provide quick-fixes for adjusting project dependencies. Learn more…

  • Java 8: Quick-fixes that help migrate for loops to Stream API calls have been improved and now support more sophisticated scenarios. We’ve also added a quick-fix that turns Stream API calls back into for loops, which is handy for debugging or exploring code.

  • Async-aware debugger: Async stacktraces is a new feature that substitutes parts of a stack trace related to asynchronous code execution with data captured from where that code is invoked. This helps you focus on what you’re debugging. An improved Smart Step Into also supports asynchronous code and lambda expressions running on other threads.

  • Better VCS: The Log panel for Git and Mercurial has new display options, the Diff dialog gets an option to Ignore imports and formatting, and File History for Git is now faster. We’ve also added Favorite Branches and Speed Search to the Branches popup for Git.

  • Search: The Find in Path dialog, which previously had added a Preview tab, has been reworked from the ground up and now shows instant results in the first place. What is more important, now you can open any selected result in the Editor simply by pressing Enter.

  • Spring: Spring Testing has been updated to support Spring Boot 1.4.3, and the upcoming Spring 5.0. Spring Data tools are updated to version 2.0 (including MongoDB, Redis, Solr, KeyValue, Gemfire, Apache Cassandra, REST, Neo4j, Couchbase, and Elasticsearch). There’s also a new Data tab in the Spring tool window which brings better repository navigation.

  • Gradle: Support for Composite Builds is much improved with the detection of includeBuild in Gradle settings and automatic project configuration.
  • Kotlin 1.1: Among other things, the new version of this JVM language introduces coroutines—the new non-blocking asynchronous API, and fully supports compilation to JavaScript. This means you can use Kotlin strings, collections, sequences, arrays and other core API in your JavaScript apps.
  • Scala: Scala plugin improvements include a simpler Project Wizard, better SBT support, additional Akka-specific coding assistance, and the new Worksheet REPL mode.
  • JavaScript: We’re bringing first-class support for Vue.js, lots of new code style options for JavaScript and TypeScript, faster and more reliable integrations with Angular, ESLint and TSLint (including language service support and TSLint-powered quick-fixes). Plus, simpler editing of project dependencies in package.json with package names and versions completion and easier running of Mocha and Jest tests with the new Run gutter icon that also displays test state.
  • GoGogland, the new Go IDE that we announced several months ago now also becomes IntelliJ IDEA Ultimate plugin.
  • Database tools: IntelliJ IDEA now allows you to transfer table schemas and data between any two databases (yes, even from MySQL to Microsoft SQL Server and back).
  • Emoji: The editor now supports Unicode emoji characters (handy for writing comments).
  • Android Studio 2.2.2: This update includes all changes from Android Studio 2.2.2.
  • Docker: The Docker plugin now supports Docker for Mac and works via “unix://”.
  • Windows: The 64-bit installer for Windows lets you give IntelliJ IDEA more RAM.

For more details about IntelliJ IDEA 2017.1, check out the What’s New page.

Your feedback is very much appreciated here in the comments, as always. For bug reports, please use our issue tracker.

P.S. Don’t forget to install Toolbox App – it’s really great at managing your IDE installations and projects. It helps you always be up-to-date with the latest releases, and safely roll back to stable versions if anything goes awry.

The Drive to Develop

About Andrey Cheptsov

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

25 Responses to IntelliJ IDEA 2017.1: Java 9, Kotlin 1.1, Spring, Gradle, JavaScript, Go and more

  1. Tim says:

    Did the included jre change? I use linux and custom vm options looked great. However 2017.1 with the same vm options enabled gives really ugly fonts again :( any suggestions?
    Options:
    -Dawt.useSystemAAFontSettings=lcd
    -Dsun.java2d.renderer=sun.java2d.marlin.MarlinRenderingEngine

  2. Marco Matessi says:

    The graphic render is different from 2016.x version? Or it is a bug?
    I have imported the settings from the previous version and the appearance is different.

    https://1drv.ms/i/s!AreT9Hob2Z8ShuVOhgB2n1KvqkvC5g

  3. Riccardo Cossu says:

    Keymap broken on Mac Os, again :-(
    At least on my Italian keyboard the Cmd + – (comment line) and Cmd + [ (and ], which is back and forward) are not working (they work on 2016.3). Nothing seems to have changed in keymap configuration…

  4. Martin says:

    Logs files defined in Run/Debug Configuration are not opening after update.

  5. Martin says:

    DDL tab is not showing changes (after refresh) for tables in Oracle database.

    • Maksim Sobolevskiy says:

      You mean, you refresh table structure in other place, but the DDL is still old? Can you please, describe in details?

      • Martin says:

        I’ve executed simple alter, like: Alter table MODIFY varchar2(25);

        Then went to DDL tab of corresponding table and it still showed old value varchar2(10), even when I was refreshing.

  6. Thomas says:

    Not too keen on “Find in Path” rework – it degrades workflow by:
    a) not allowing to use external clipboard manager – focus is lost and find in path window is auto closed
    b) changing active tab while on find in path closes search window – same issue
    c) f4 is disabled which is very natural action for same hand coordination after pressing ctrl+shift+f – there should/is no need to disable f4 which is IDE wide “move to” key (VCS window, etc) and doesn’t conflict with enter functionality

    • Jeff says:

      I do like that it now shows the results instantly but my biggest annoyance is that you took away the close window button. When I’m done I have to or click outside of the window to close it. While these aren’t hard to do, they are unintuitive. Why take away the standard Windows close button?

  7. Marco Matessi says:

    The graphic render is different from 2016.x version? Or it is a bug?
    I have imported the settings from the previous version and the appearance is different.

  8. Swen says:

    After update to IntelliJ IDEA 2017.1 can not longer open Tools – Deployment – Configuration setup form. Installed IntelliJ IDEA 2016.3.5 alongside IntelliJ IDEA 2017.1 -> now both can not open: Tools – Deployment – Configuration… Menu selection simply does not do anything.

    Windows 7 Pro x64. jdk1.8.0_121 / jre1.8.0_121

  9. Pavel Kropachev says:

    Hello!

    I’ve observed ugly font for system menu and controls in Ubuntu 16.04 (default Ubuntu font). All is ok in code editor. Bundled JDK is used (openjdk 1.8.0_112 [bundled]). I didn’t see such problem in version 2016.3.5.

  10. Jon says:

    Issues with cfscript now. Causes freezing of that file/tab as the suggestion/auto-complete window appears.

  11. Eric B. says:

    I don’t have any “real” data to back this up, but anecdotally I notice the performance of 2017.1 to be very bad compared to the prior version 2016.3 that I upgraded from. We have relatively large codebase, but 2016.3 handled it fine.

    However, after upgrading to 2017.1 and applying the same memory settings, it feels very sluggish. There are noticeable pauses at inconsistent times as I click from one part of the IDE to another.

    Is anyone else reporting this change in behavior?

    • Eric B. says:

      Thankfully, I am no longer having this issue.

      My original statement of having applied the same memory settings was not exactly correct. In prior releases, I had applied memory settings via IntelliJ IDEA 2017.1\bin\idea64.exe.vmoptions. However, in 2017.1 I attempted to apply memory settings at {user_home}\.IntelliJIdea2017.1\idea64.exe.vmoptions .

      I need to do more testing to be sure, but it seems like the {user_home}\.IntelliJIdea2017.1\idea64.exe.vmoptions approach did not really affect the memory settings.

      When I went back to the original way of applying to IntelliJ IDEA 2017.1\bin\idea64.exe.vmoptions, I see the memory settings taking affect and the IDE is working smoothly again.

  12. Hi,I log on to your blogs named “IntelliJ IDEA 2017.1: Java 9, Kotlin 1.1, Spring, Gradle, JavaScript, Go and more | IntelliJ IDEA Blog” regularly.Your writing style is witty, keep up the good work! And you can look our website about proxy server list.

Leave a Reply

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