Early Access Program

What’s new in IntelliJ IDEA 2019.3 EAP 2?

Our work on the next major version of IntelliJ IDEA is in full swing. We have been checking and polishing the IDE during our IntelliJ Quality marathon, and today we are ready to give you the second EAP build for the upcoming IntelliJ IDEA 2019.3, which comes with huge pack of highly anticipated fixes and improvements.

As usual, the EAP builds for IntelliJ IDEA Ultimate are free to use, but they will expire within 30 days of the build date.

Improved “Compare with Current” view

With v2019.2, we changed the ‘Compare with Current’ action into 2 different actions: ‘Compare with Current’ and ‘Show Diff with Working Tree’. The updated ‘Compare with Current’ action shows the difference in commits, while the ‘Show Diff with Working Tree’ action shows the file diff.

Based on the feedback we’ve been receiving we have continued to work on the ‘Compare with Current’ view and have added a bunch of usability improvements to make the display of the comparison result more clear.

Firstly, we added the tab title which specifies the branches that are compared. Also, we added a bar that clarifies the comparison direction. And now when the view is empty the IDE displays an explanation why.
Also, there is a new ‘Swap branches’ action that swaps the comparison direction of the branches.


We plan to improve this view further and our next step will be to add more information about the reversed comparison to the bar of the Compare tab. This will make it more clear if it is worth swapping branches. Here is the ticket you can use to follow the progress of this task or to share your feedback: IDEA-222141.

Contrast scrollbars

One more usability issue has been resolved – now you can make the scrollbars more visible. Go to Preferences/Settings | Appearance & Behavior | Appearance and enable the “Use contrast scrollbars” checkbox.
This new option will be backported to IntelliJ IDEA 2019.2.3 as well.


Please note, that starting from v2019.2 macOS users, can configure the editor scrollbar color and opacity at Preferences | Editor | Color Scheme | General | Editor | Vertical Scrollbar. Please let us know if you need this feature on Windows or Linux by upvoting this ticket: IDEA-102320.

Ability to search in a selected area when using the Find action

It’s now possible to search only in a selected area using the Find action (cmd+F / Ctrl +F). Simply select the code piece you need in the editor and invoke the Find action and the IDE will perform the search only in the selected area. If you need to extend the search area and perform the search within the whole file, press the cmd + F / Ctrl + F shortcut a second time or alternatively toggle the In Selection option from the bar.
Previously the In Selection option was available only when you were using the Replace action (cmd+R /Ctrl +R).


Support for annotation processors was greatly improved for Gradle projects

The upcoming IntelliJ IDEA 2019.3 now creates an Annotation Processing profile based on the Gradle configuration and assigns relevant modules with it. All the required files are generated during a build.
Also, the IDE now supports the annotationProcessor dependency configuration introduced in Gradle 4.6.

Other notable fixes worth mentioning:

  • Fixed the performance issue that caused the slow execution of the “Resolving external annotations” background task: IDEA-200003.
  • Fixed the issue that caused the focus loss when switching between IDE windows using Cmd ~ on macOS: IDEA-216019.
  • The IDE supports native password storage on Linux: IDEA-185926.
  • Keyboard navigation works in the Debug tool window: IDEA-167805.
  • It’s now possible to resize the project area if the editor tabs are on the right: IDEA-147414.

The bundled JBR11 was updated to v11.0.4+10-b480.2, which among other changes, fixed an issue with the Navigation Bar.

For more details please read the IDE and JBR release notes.

Get the new EAP build right now! Don’t hesitate to share any and all feedback with us in our issue tracker!

Happy Developing!

Comments below can no longer be edited.

19 Responses to What’s new in IntelliJ IDEA 2019.3 EAP 2?

  1. Avatar

    Joachim says:

    September 19, 2019

    Thank you for the new option of scrollbar colors! Scrollbars were a bit irritating since this was changed a few years ago. Doing a lot of performance and usability work for 2019.3 is much appreciated. Thanks!

  2. Avatar

    Mike says:

    September 19, 2019

    Is it possible to use IDEA 2019.3 running on top of JDK 13 or it must use JBR 11?

    • Avatar

      Joe says:

      September 20, 2019

      Why do you want to change IntelliJ’s runtime? What benefit are you looking for?

      • Avatar

        Mike says:

        September 20, 2019

        Mainly due to JEP 351 ZGC Uncommit Unused Memory.

        • Avatar

          Konstantin Bulenkov says:

          September 23, 2019

          It’s possible in theory, but not recommended. JBR11 contains a number of important UI fixes/improvements which is not backported to OpenJDK.

  3. Avatar

    Yihao says:

    September 20, 2019

    I can feel 2019.3 has a significant startup speed improvement again.
    It now makes sense that JetBrains not making a VSCode-like lite editor 😛
    Keep it up, guys!

  4. Avatar

    Steven says:

    September 20, 2019

    Personally, I would be happier if this product worked on Mac OS Catalina vs getting pretty scrollbars. That OS will be released in the next 30 days or so. Do you have plans to support it in 2019-3 at all? As of now, in many cases you can’t even get past the splash screen or invoke the ‘Open Project’ window without some PITA workarounds.

    • Avatar

      Arseniy Nisnevich says:

      September 24, 2019

      Hi Steven,

      We plan to fully support the stable version of Catalina. During the beta period, running may be unstable because the system is still under development. For instance, due to this, at the moment we use java-based file chooser instead of the native one on Catalina.

      Also, there was a massive problem with crashing on startup, but it has already been fixed: https://youtrack.jetbrains.com/issue/JBR-1639

      Could you please file a new issue and explain what happens when you can’t pass the splash screen? Please, provide IDE log files also. Thanks. https://youtrack.jetbrains.com/newIssue

  5. Avatar

    Christopher Woods says:

    September 20, 2019

    Is there a timeline for enabling the plugins that are disabled for this EAP? I realize you have little control over plugins developed by third parties, but these plugins include Python and Go, both Jetbrains developed.

    • Avatar

      Alexander Zolotov says:

      September 23, 2019

      Hi Christopher.

      Go plugin was available for the EAP a day before EAP was published. Do you have any problems with its installation? Could you attach logs and describe steps to recreate the problem in our issue tracker at https://youtrack.jetbrains.com?

      As for Python plugin, it was our fault, we’ve already uploaded it. Sorry about the inconvenience.

      • Avatar

        Christopher Woods says:

        September 23, 2019

        Hello Alexander,

        Thanks for your reply. I’m just going on the message displayed in the update window that lists “Plugins incompatible with the new build found: LiveEdit, Go Template, Go, .ignore”


        • Avatar

          Alexander Zolotov says:

          September 23, 2019

          They are incompatible and thus need to be upgraded. Is the update available for you?

          • Avatar

            Christopher Woods says:

            September 23, 2019

            They are. It was not obvious that they would be available until after I installed the latest EAP. Thanks for your help.

  6. Avatar

    Fabio says:

    September 20, 2019

    Why is the PHP plugin not updated? It seems to be available in a separate download but it can’t be updated automatically in settings > plugins.
    Do we need to update it manually?

  7. Avatar

    Mike says:

    September 23, 2019

    The split editor bug introduced in 2019.3 is keeping me from using the EAP (file opening in wrong editor). I use split editors all the time and this is a blocker for me. From what I have used it seems pretty stable, but that split editor problem makes it very difficult to use.

    I have opened a bug but there has been no movement on it.

  8. Avatar

    Salvatore Pelligra says:

    September 24, 2019

    Hello, thanks for this Early version. I’m having quite some trouble using the new Git commit.
    When I click on “VCS > Commit”, then “Version Control > Local changes” opens up instead of the previous “Commit Changes” window, which was much, much more useful.

    I’m missing something or Commit Changes functionality has been removed? This quite break my flow.

    PhpStorm 2019.3 EAP
    Build #PS-193.3519.40, built on September 23, 2019
    PhpStorm EAP User
    Expiration date: October 23, 2019
    Runtime version: 11.0.4+10-b480.2 x86_64
    VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
    macOS 10.13.6
    GC: G1 Young Generation, G1 Old Generation
    Memory: 2048M
    Cores: 8
    Registry: run.processes.with.pty=TRUE, search.everywhere.configurations=false
    Non-Bundled Plugins: IdeaVIM, de.espend.idea.laravel

    • Avatar

      Dmitriy Smirnov says:

      September 25, 2019

      > Commit Changes functionality has been removed

      Of course, no. Modal Commit Dialog was removed though, and functionality has moved to Local Changes.

      So, VCS – Commit action indeed navigates to the Local Changes, selects the files to commit and puts focus to the Commit message field. Clicking Commit button (or Ctrl+Enter, as it used to be with the modal) invokes commit.

  9. Avatar

    Joachim Beckers says:

    October 4, 2019

    Please make the “Find in selection” thing non-default. This completely breaks the normal workflow of “select some text”, “Ctrl+F”, “find the fscking selected text in the file like you would expect damnit!”


  10. Avatar

    Nadezhda says:

    January 15, 2020

    Hello everyone, could you please support with the following question:
    Is it any possibility in IDEA 2019.3 to make settings in such way so that when class name in java file was changed ( using “Refactor”) the mainClassName in build.gradle file would automatically changed too? In previous versions it was possible with Button “Do Refactor”. Thank you in advance.

Discover more