IntelliJ IDEA 2018.2.1 EAP is out!

Posted on by Zlata Kalyuzhnaya

We released IntelliJ IDEA 2018.2 just yesterday, and today we are ready to open an Early Access Program for the first bug-fix update of v2018.2! Grab the freshly made IntelliJ IDEA 2018.2.1 EAP build from the Confluence website or, via Toolbox App, or if you’re running IntelliJ IDEA 2018.2 – install the patch.

Please note that this EAP build requires an active license for IntelliJ IDEA Ultimate.

For a start, now when you work with a Gradle project and choose the Use gradle ‘wrapper’ task configuration option, IntelliJ IDEA doesn’t modify any wrapper-related files on project synchronization or import.

We are continuing our work on the Groovy 3.0 support, and with this build we’ve now added support for: an enhanced classic Java-style for loop, multi-assignment in combination with a for loop, and Java-style array initialization.

We’ve also fixed a couple of other bugs worth mentioning:

  • Structure panel now shows correct data again: IDEA-183801
  • New files are shown in the package view: IDEA-195578

Check out the release notes for the complete list of changes

Try IntelliJ IDEA 2018.2.1 EAP and don’t forget to share your feedback with us! As always on: issue tracker, discussion forum, Twitter!

Happy developing!

Comments below can no longer be edited.

6 Responses to IntelliJ IDEA 2018.2.1 EAP is out!

  1. Taras Tielkes says:

    July 26, 2018

    The rendering artifacts I was seeing (Windows 7, JetBrains JRE) with the 2018.2 release seem to have been fixed in this EAP build.

    Thanks 🙂

    • Edoardo Luppi says:

      July 27, 2018

      Which artifacts?

  2. Rado says:

    July 27, 2018

    Hi,

    any plans to fix the mess Android plugin is doing in a multi-module project?

    https://youtrack.jetbrains.com/issue/IDEA-191076
    https://youtrack.jetbrains.com/issue/IDEA-189684

  3. Bluishoul says:

    July 31, 2018

    It seems that refresh debugging with gradle bootRun in IDEA 2018.2 wouldn’t kill java process.

    • Greg says:

      August 1, 2018

      This one is really aggravating…forcing me to manually kill processes.

    • Peter Kirby says:

      August 5, 2018

      +1

Subscribe

Subscribe for updates