Early Access Program

IntelliJ IDEA 2018.2 EAP2: Breakpoint intentions, enhancements in Code Refactoring and more

We opened an Early Access Program for IntelliJ IDEA 2018.2 just one week ago, but today we are ready to deliver a new EAP build with some cool new features. Update from within the IDE, via Toolbox App, or download the new EAP build directly from the website. Here’s a little more insight into what this new build has in store for you.

JVM debugger

We always have some new improvements for you in our debugger. The upcoming IntelliJ IDEA 2018.2 brings new breakpoint intentions.

While debugging in IntelliJ IDEA, you can limit the breakpoint to hit only particular object instances, or define the class where you want the breakpoint to be hit or the classes where the breakpoint should not be hit. These nice capabilities, however, required editing the properties of a particular breakpoint by hand – setting different filters, lots of button clicking, and so on.

Now, while debugging a Java project, you have some handy intention actions available:

– stop only in class
– do not stop in class
– stop only in the current object

No more fiddling about with the Breakpoint dialog and its filters! When you’re in a debugging session, simply press Alt+Enter and the IDE will offer you the new breakpoint intentions, along with all the other available intentions!


Code refactoring

The upcoming IntelliJ IDEA 2018.2 introduces a new preview panel for the Extract Method refactoring. This can be quite useful when you perform refactoring on code fragments with duplicates.

Invoke the Extract Method refactoring using the shortcut (Ctrl+Alt+M on Windows/Linux or Cmd+Alt+M on macOS) or by selecting Refactor | Extract | Method. The IDE will show you the Extract Method dialog. Click the Preview button to preview all the changes in one place.

The IDE now provides you with an ability to review the results of your refactoring before you make any actual changes.


In addition, we have enhanced our Maven support so that IntelliJ IDEA now correctly parses POM even when the parent POM reference contains a property placeholder. Also, the IDE now resolves properties from the configuration files: .mvn/maven.config and .mvn/jvm.config.

For further details on the changes, please consult the release notes.

You can try out these new features right now in the latest EAP build! Download it today!

And don’t forget that we are always looking forward to your feedback in our issue tracker, here in the comments, or on Twitter.

Happy developing!

Comments below can no longer be edited.

9 Responses to IntelliJ IDEA 2018.2 EAP2: Breakpoint intentions, enhancements in Code Refactoring and more

  1. Avatar

    Edoardo says:

    May 22, 2018

    Awesome guys! Keep up increasing performance. I use IntelliJ in a virtual desktop through Citrix and it’s becoming a bit heavy (for example, inspections with 3000 lines of code require 4-5 seconds to finish and update the editor)

    • Avatar

      Edoardo says:

      May 22, 2018

      Clarification: 4-5 seconds not the first time, but when I use them to correct my code.

    • Avatar

      Edoardo says:

      May 22, 2018

      That’s the CPU snapshot name: IU-182.2574.2_Edoardo Luppi_22.05.2018_19.53.24.snapshot
      I upload it to your server.

  2. Avatar

    jtonic says:

    May 23, 2018

    That’s cool!

    I played a bit with the new breakpoint intentions and I was pleasantly surprised to see these features are also available in kotlin.


  3. Avatar

    Fabio Chelly says:

    May 27, 2018

    The new icons are beautiful. I really love them but what happened to the beautiful blue focus rect on buttons that appeared with the latest 2018.1 versions in Darcula theme? It has been replaced by an ugly grey/blue line in the 2018.2 version. Is it possible to go back to the blue only focus rect?

  4. Avatar

    Fabio Chelly says:

    May 27, 2018

    On further consideration, it’s not the color that was different but I think there was a 1 pixel empty space between the button and the focus rect that was far more beautiful

    • Avatar

      Olga Berdnikova says:

      June 13, 2018

      Hello, Fabio! Thanks for your feedback! About the focus outline with an empty space between it and the button. We got feedback that such outline looks too noticeable and, thus, distracting. That’s why we changed it to the version without the empty space. Had to change colors too so the focus outline is visible over the button. I’m sorry you find the new look ugly.

  5. Avatar

    Piotr says:

    July 26, 2018

    I updated the IntelliJ today and noticed that I when debugging multiple nested lambdas, the local variables aren’t displayed in Variables list despite being clearly visible (even auto-complete suggests them). I tried to make some other example code that could reproduce it but it seems for simpler examples everything is fine. Were there some changes recently to variables in debugger because previously it worked fine?

    • Avatar

      Vitaliy Bibaev says:

      July 26, 2018

      Hello Piotr, thanks for your feedback.

      Could you please provide us more details about your problem. What version of JDK do you use? There were some issues with the visibility of local variables in lambdas before 8u60 (https://youtrack.jetbrains.com/issue/IDEA-126257).

      Also, make sure lost variables are local for the lambda at the debugger stop because a visibility in the completion does not mean that value is a local variable.

      It would be great if you reproduce this behavior on a simple project. You can try to repeat the structure of nested lambdas and lost variables.

Discover more