IntelliJ IDEA 2019.3 Hits Beta

IntelliJ IDEA 2019.3 Beta is available now!  The major changes have been implemented, and we’re ready for you to try it out and share your opinions with us.

Our focus for this release has been performance and quality, although there have been some notable new features as well.  We’ve covered a lot of things already in our EAP blog posts, but here are some of the highlights.

blog@2x

Performance

Improvements

New

This release also includes all the changes from Android Studio 3.5.

We’ve worked hard on this release with you, the developers, in mind. We’d love you to try out the Beta and we really want to hear any feedback you have, especially while there’s still time to add polish before the official release. You can leave feedback here in the comments, in our issue tracker, or on Twitter.

Keep an eye on this blog and the YouTube channel for our upcoming screencast on the features in 2019.3 which are most interesting to Java developers.

This entry was posted in Beta Releases and tagged , . Bookmark the permalink.

12 Responses to IntelliJ IDEA 2019.3 Hits Beta

  1. Gecp says:

    after reimporting pom.xml

    java.nio.charset.IllegalCharsetNameException: ${project.encoding}
    at java.base/java.nio.charset.Charset.checkName(Charset.java:308)
    at java.base/java.nio.charset.Charset.lookup2(Charset.java:482)
    at java.base/java.nio.charset.Charset.lookup(Charset.java:462)
    at java.base/java.nio.charset.Charset.forName(Charset.java:526)
    at org.jetbrains.idea.maven.importing.configurers.MavenEncodingConfigurer.getCharset(MavenEncodingConfigurer.kt:97)
    at org.jetbrains.idea.maven.importing.configurers.MavenEncodingConfigurer.fillResourceEncoding(MavenEncodingConfigurer.kt:59)
    at org.jetbrains.idea.maven.importing.configurers.MavenEncodingConfigurer.configure(MavenEncodingConfigurer.kt:42)
    at org.jetbrains.idea.maven.importing.MavenProjectImporter.lambda$importProject$1(MavenProjectImporter.java:146)
    at org.jetbrains.idea.maven.utils.MavenUtil.lambda$runInBackground$5(MavenUtil.java:482)
    at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:238)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:834)

  2. Sebastian says:

    Unfortunatley, the bugs using play!framework (v1) projects still exist, which makes 2019.3 still unuseable for theses projects :(

    See my comments (and bug reports) for EPA 8: https://blog.jetbrains.com/idea/2019/10/whats-new-in-intellij-idea-2019-3-eap8/#comment-505465

  3. Jens says:

    Is this a Beta or an EAP Version?

    • Trisha Gee says:

      The latest version available is a Beta. The text on the download page does talk about early access versions, it’s general text that is applied to releases that aren’t the full production release.

      • Jens says:

        My current Version is 2019.2.4.
        The update config is “beta or higher” but it finds no updates.
        The skip update list is empty.

  4. Henjo says:

    This bug makes this version unusable:
    https://youtrack.jetbrains.com/issue/IDEA-224676

    It makes building + running webapplications using Tomcat, Spring boot and other application servers impossible, since the app server already starts during the maven build.
    Before this version the app startup actually waits until the maven build is complete.

  5. Alain says:

    is it possible to fix this regression
    https://youtrack.jetbrains.com/issue/IDEA-221550
    in 2019.3 ? or will this regression appear in all 2019 version :/

  6. Steve says:

    There seems to be a problem with all setting textboxes behavior on macos as well
    The cursor behaves very weird. In the start of the string (first 4 characters it works as expected), 5th character it jumps to the 6th, but still “edits’ the fifth. By the end of the string it’s 4 characters wrong (and 4 spaces past the end visually)….

  7. Elias says:

    Now that you have laid the foundation for nosql databaseses in the form of MongoDB, will you also begin work on supporting other nosql db’s? For example, being able to have ElasticSearch as a database source in IntelliJ would make a huge improvement to my day to day workflow.

Leave a Reply

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