Early Access Program

IntelliJ IDEA 2019.1 Release Candidate is Out!

A Release Candidate of the upcoming IntelliJ IDEA 2019.1 is available to download! Grab the newest build and share your feedback right now, as we plan to release v2019.1 next week.

Please note that this build requires a license for IntelliJ IDEA Ultimate.


With each release, we are not only adding new features but also working to enhance the existing functionality. In the upcoming IntelliJ IDEA 2019.1, we’ve made Maven diagrams better.

You can now quickly find the conflicts and duplicated dependencies by utilizing the ‘Show Conflicts/Duplicates’ option.


Also, you can select a node and view all the paths to it by choosing ‘Show Paths: Root -> Selection’.


Now, you can view only the dependencies of the selected nodes. To do that, click ‘Show Neighbors of Selected Nodes’. To view the dependencies for several nodes at once, hold the Shift key and select all needed nodes.


For better readability, switch to the Borderless View.


Docker support has reached the debugger

With the upcoming IntelliJ IDEA 2019.1 you can now attach the debugger to a Java application running inside a Docker container.
The IDE now allows debugging inside containers that are built from a Dockerfile, or created using Docker compose (docker-compose.yml).


You need to create a remote debug configuration and in the ‘Before launch:’ field add the Docker run configuration.

Screen Shot 2019-03-21 at 16.46.32

We plan to publish a detailed tutorial on Debugging Java applications in Docker in our documentation.

We’ve also updated JetBrains Runtime 11 to v11.0.2+9-b159.30. The full JBR  release notes can be found here.

The IDE release notes are available here.

Download the latest build of the upcoming v2019.1 and see how this works for you. Any feedback is highly appreciated here in the comments, in our issue tracker, or on Twitter.

Happy Developing!

Comments below can no longer be edited.

16 Responses to IntelliJ IDEA 2019.1 Release Candidate is Out!

  1. Avatar

    Alex Katlein says:

    March 21, 2019

    That’s nice and all, but when are we getting those kinds of diagrams for Gradle projects?

    This is really something I have been waiting on for ages and I don’t think I’m alone.

  2. Avatar

    Hi says:

    March 22, 2019

    where is this diagram? How to launch it? “Run… | Actions” popup cannot find it.

    • Zlata Kalyuzhnaya

      Zlata Kalyuzhnaya says:

      March 25, 2019

      In the Maven Projects tool window, right-click the desired sub project and choose Show Dependencies, or Show Dependencies Popup

  3. Avatar

    Vicky says:

    March 25, 2019

    When are the RC builds and Release version going to be available on
    intellij repository https://www.jetbrains.com/intellij-repository/releases

  4. Avatar

    Reto says:

    March 27, 2019

    Programmers of our company have reported that they can no longer run or debug our project with IDEA 2019
    because of a problem with System.loadLibrary (java.lang.UnsatisfiedLinkError: c:\path\to\a.dll: Can’t find dependent libraries)
    It works with IDEA 2018 on the same machine. Same JDK used in project. Both use Windows OS.
    We compared the “start” command line (first blue line in the IDEA console) and its the same, expect of the path to the agent, of course.
    We also compared workdir and java.library.path. So we assume that the IDEA agent cause the problem.
    (Sorry, no reproducer and or youtrack report from me. Just as a info. I will spend time on that at the earliest when 2019.1 was released.)

    • Zlata Kalyuzhnaya

      Zlata Kalyuzhnaya says:

      March 28, 2019

      Thanks for the feedback! IntelliJ IDEA 2019.1 is now released, and we’ll highly appreciate if you’ll download and try it. If this issue will be reproduced, please create an issue in our bug-tracker with more details.

  5. Avatar

    Reinhold Früsmer says:

    April 13, 2019

    We are facing the same issue with latest IntelliJ IDEA 2019.1 (Ultimate Edition) Build #IU-191.6183.87. I’ve analyzed it with Process Monitor and it seems to be a path problem, i will file an issue for that in Youtrack.

    In the meantime you can use this workaround: add the path where the native binaries are stored to the PATH environment variable, e. g. in the run configuration like this:


Discover more