Early Access Program Features

IntelliJ IDEA 16 EAP Improves Debugger and Adds Git Worktree Support

Great news, everyone! A fresh weekly IntelliJ IDEA 16 EAP is out and ready, packed with bugfixes and new features as usual. The noticeable changes affect the debugger, VCS integrations, and user interface.


Now when debugging a Java application, you can use Groovy expressions with Evaluate Expression and Watches. Previously you could do that only when debugging Groovy code. This is good because Groovy expressions are much shorter and more expressive (especially when you work with collections.)


This feature requires a Groovy runtime library in the classpath.

Also, we’ve made it easier to debug multiple threads. Until now, stepping over one thread meant IntelliJ IDEA would also resume all the other threads (that stopped at breakpoints for which Suspend policy was set to All). Now you can change this behavior by enabling the Resume only the current thread option in Settings > Build, Execution, Deployment > Debugger > Stepping.


VCS integration

Git users will be happy to know that IntelliJ IDEA now supports worktrees. This feature was introduced in Git 2.5 to make working with clones of a single repository simpler, because instead of making a repository clone you could create a lightweight worktree. The good news is that now IntelliJ IDEA supports those worktrees, so you can work with them just like you do with regular repositories.

The look and feel of Git Log has been updated with a better-looking toolbar and thinner splitters, and the table headers have been removed.


Show/Find usages

Talking about user interface, we have improved the speed-search in the Show usages popup. Now, when you use it, the matches are highlighted for easier navigation.


The speed-search in Find usages tool window has also been improved in another way: now it looks through the entire contents of the tool window text.

Last but not least, if you run any code cleanup inspection via Run Inspection by Name, you will now be offered to apply the quick-fix right away in the dialog.


That’s it for now. We hope you’ll find these enhancements useful and give us your feedback and bug reports on our discussion forum and in the issue tracker.

Develop with pleasure!

Comments below can no longer be edited.

7 Responses to IntelliJ IDEA 16 EAP Improves Debugger and Adds Git Worktree Support

  1. Avatar

    Anton says:

    February 4, 2016

    Thanks, will try

  2. Avatar

    FingolfinTEK says:

    February 4, 2016

    Fantastic! Keep up the good work 🙂

  3. Avatar

    Spencer says:

    February 4, 2016

    Cool! Any chance of other JVM langs making their way into watch expressions (like Kotlin, for example)?

  4. Avatar

    Palanivelrajan says:

    February 4, 2016

    Thanks. I am trying out EAP version. I am working on a gradle project and look like some recent changes that you have done in EAP 16 to address some gradle issues is creating a new issue for me.


    Can the development team provide me some inputs on this issue?

  5. Avatar

    Alex says:

    February 4, 2016

    Wasn’t the ‘Resume only the current thread’ functionality already available ?
    1. Set a debug point.
    2. Right click on it.
    3. Check Thread (by default All is checked).

    • Avatar

      Andrey Cheptsov says:

      February 5, 2016

      I has changed a little bit the text to make it clearer. The new option affects those breakpoints that were set to “All”.

  6. Avatar

    Selters says:

    February 5, 2016

    Really like the new find-usages. Very nice. Keep making good stuff like this! 🙂 It’s actually small things like this that often has a huge impact on my productivity. Insta-preview per-key-stroke when doing a search-in-path that was released in the last version is something I use all the time now – it makes the whole difference.

    The UI for git log also looks better, indeed.

    Feature request: Improve the Scala Worksheet view. The current split view is very space-hungry and doesn’t work so well on e..g. a laptop screen (which is what all the devs in my team are using). Would be really nice if you could display the result in-line in a smart way like you do in debug-mode (and the way scala IDE does it).

Discover more