IntelliJ IDEA 2018.2.3 is here!

IntelliJ IDEA 2018.2.3 is now released! Download the third bug-fix update for v2018.2 from our website or install it with ToolBox App.

This minor update comes with various bug-fixes and some improvements worth noting too:

  • Ability to open HTML files in Edge using the Open in Browser action.
  • Fixed IntelliJ IDEA freezes.
  • Git: The built-in SSH doesn’t fail when Git protocol version 2 is enabled.
  • Fixed regressions in Mercurial support.
  • Docker: the IDE now validates Command line options and reports unknown options.
  • Docker: volume mounting now works on Windows using Linux containers.
  • Minor Gradle bug-fixes.

For more improvements and the full list of fixes, check out our release notes. Remember to report any issues you encounter!

By the way, stay tuned for the start of the Early Access Program for IntelliJ IDEA 2018.3. It’s just around the corner!

Happy developing!

About Zlata Kalyuzhnaya

IntelliJ IDEA Marketing Manager at JetBrains. twitter: @ZlataKalyuzhnay ‏
This entry was posted in EAP Releases and tagged , . Bookmark the permalink.

23 Responses to IntelliJ IDEA 2018.2.3 is here!

  1. Edoardo Luppi says:

    I’ve seen colored icons came back with 2018.3, do you confirm this?

  2. Arnold says:

    A link to the release notes where they are mentioned would be helpful.

  3. Lil Sebastian says:

    Why did you guys change buttons around and remove the “+” button to add a new change list in the Version Control tab, hiding it under a menu now? The lack of colors on the buttons prevent them from standing out and you’re making people get used to new buttons for no reason.

  4. xiaoyangzhang says:

    I use Mac. Since 2018.2.1,though the IDEA supports TouchBar,but the KeyMap Option+Enter ,which described as “show Intention Action” ,is not in use.When I press the KeyMap Option+Enter,the TouchBar shows Something. How can I solve this?

  5. Adam says:

    Why some updates allow the Idea to patch itself and some (like this one) require me to download a full install and do it from scratch?
    Is this somehow related to my environment? Or affects everyone, just depends on the way the release was prepared? The previous minor release was self patching…

  6. Christian Beikov says:

    Why is this still not fixed? This is ridiculous that you don’t give such issues a higher priority. People actually waste a lot of time because of the inability of the IDE to flush changes properly to disk when context switching!

  7. Jwaiwit says:

    Since 2018.2.1 build, when debug Java It’s can’t rerun, previous process not terminate.
    So end up with port already in use (need to kill process manually)

Leave a Reply

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