IntelliJ IDEA 2019.1 hits Beta

The upcoming IntelliJ IDEA 2019.1 goes Beta! To install IntelliJ IDEA 2019.1 Beta, download it from the website, update from our Toolbox App, or use a patch update.

The Beta builds are sufficiently stable compared to the EAP builds, but some issues may still occur. If they do for you, please report them to our issue tracker.

Since the opening of IntelliJ IDEA 2019.1 EAP, we’ve teased you with previews of the most notable changes to expect and this Beta stage seems to be a good time for an overview of some of the Java improvements that are coming your way in this next major version. Watch now.

Let’s take a more detailed look at a few of the big changes that are in this build.

Support for Java-style Lambda syntax of Groovy 3.0

Earlier in IntelliJ IDEA 2018.2, we added initial Groovy 3.0 support. With the upcoming IntelliJ IDEA 2019.1, we are taking it even further by supporting the experimental Groovy 3.0 feature highly anticipated by the Groovy developers – Java-style Lambda syntax.

IntelliJ IDEA now provides editing support including code completion, highlighting, and type inference.


Groovy intentions and inspections work properly inside the lambda body.


Now formatting is also available for Java-style lambdas. We’ve added a couple of specific new Java-style lambda options that can be found in Preferences Settings | Editor | Code Style | Groovy. On the ‘Wrapping and Braces’ tab, look for Braces placement | In lambda declaration and Keep when reformatting | Simple lambdas in one line. On the Spaces tab, we’ve added Around Operators | Lambda arrow.

That you can now debug Java-style lambdas should be useful, too.


So far we’re only getting started with supporting the Groovy 3.0 Java-style lambda syntax. We plan to extend this functionality in future releases of IntelliJ IDEA and add support for various refactorings.

Fixes linked with JetBrains Runtime 8

Last but not least, JetBrains Runtime 8 was updated to 1.8.0_202-release-1483-b31 and with this version we’ve fixed a few things like:

  • DPI detection which was broken on KDE in 8u202 was repaired: JBR-1200.
  • Windows native file dialogs with the new Common Item Dialog API was implemented: JBR-1216.
  • The issue with jittering WebView scrolls was resolved: JBR-1218.
  • Custom Window Frame decoration is supported: JBR-1228.

Note that early access to IntelliJ IDEA 2019.1 is available to you with the new JetBrains Runtime 11. Try it and let us know what you think!

We encourage you to download the Beta build right away and give it a good try! We welcome your feedback, so please reach out to us in our discussion forum, issue tracker, twitter, or here in the comments.

Happy Developing!

About Zlata Kalyuzhnaya

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

14 Responses to IntelliJ IDEA 2019.1 hits Beta

  1. Have been using the new version with the JDK11 runtime. Would it be possible to spend a blog post on why one would prefer the JDK11 over JDK8 …

  2. Elior Boukhobza says:

    Custom Window Frame decoration is supported: JBR-1228.

    What does that mean?

  3. Quazi Irfan says:

    I like the smarter stack trace feature. But is it able to take me to the variable that is null?

    I know C# has can name which variable is null, and I was told JVM can not do it since the name of the variable is lost during Java Byte Code translation.

    • Tagir Valeev says:

      No, unfortunately we cannot position the caret to NullPointerException (NPE) cause, mostly because there’s no additional information and single line may have several NPE causes. On the other hand adding detailed message to NPE report is actively considered in OpenJDK now (see ). Thus it’s quite possible that additional information will be added in Java 13 or 14. If this happens we will use this information for precise caret position.

  4. Downloader says:

    How to download this Beta on Linux?

    1. Go to, select Runtime 8 -> redirect to download exe
    2. Select Runtime 11 and,rc&platform=linuxJDK11 got this link: and after that this error message: {“errors”:[{“code”:404,”message”:”Can’t find download link for distribution linuxJDK11″}]}

    Same story was with EAP…

  5. Frantisek says:

    Is there a list of new features/improvements compared to 2018.3 for us who don’t have time to go through all the EAP blogs?

  6. Mike says:

    Gradle composite builds are _still_ totally broken. They have been since early in the EAP. I opened an issue and it was closed quite quickly with the information that the problem was caused by the Kotlin plugin.

    When can we expect to see this fixed? Hopefully before final release? Surely gradle composite builds is a feature many people depend on, it can’t be that esoteric.

Leave a Reply to Edoardo Luppi Cancel reply

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