IntelliJ IDEA 16 EAP 144.2608 is Out

If you’ve already tried IntelliJ IDEA 16 EAP announced last week, you’ll be glad to know that we’ve just released a new build.

With this build IntelliJ IDEA and the whole IntelliJ platform migrates to Java 8. Users won’t be able to launch the IDE under a JDK older than Java 8. It means plugin developers now can use Java 8 features in their code. This change affects the master branch (144.* builds) and further major releases in Spring, 2016. The bugfix updates (143.*builds) will remain compatible with Java 6.

The inspection that finds code duplicates now has an option to ignore generated code.

Screen Shot 2015-12-29 at 19.38.27

Also, we added a new inspection called Declaration access can be weaker. When enabled, it prevents making fields, methods and classes unnecessary public.

Screen Shot 2015-12-29 at 19.35.59

This inspection may result in false positives if the corresponding field, method or class is supposed to be used outside the project only as a public API. Enable it on the scopes you need in Settings or simply run it for any scope using Run Inspection by Name via Alt + Shift + Ctrl + I (Alt + Shift + Ctrl + I for OS X).

For Mercurial we made it possible to compare revisions of a file between branches. Previously it was only possible to compare revisions within a single branch.

Screen Shot 2015-12-29 at 19.49.32

For the complete list of changes, refer to the release notes.

After you try the new build, don’t forget to share your feedback with us on our discussion forum or directly in the issue tracker.

Develop with pleasure and happy New Year!

About Andrey Cheptsov

Part-time dreamer. JVM/JavaScript geek. IntelliJIDEA Marketing Manager at JetBrains.
This entry was posted in EAP Releases, New Features and tagged . Bookmark the permalink.

13 Responses to IntelliJ IDEA 16 EAP 144.2608 is Out

  1. Mikhail Fursov says:

    Guys, with JDK you provide there are no fonts rendered at all on old Linux systems (like Ubuntu 12.04). And some companies still use this OS version for internal development.

    Please do not ignore us and do not make IDEA depend on features in your custom JDK. Because today original JDK is is the only option to run new IDEA on old Linux.

  2. RusAlex says:

    This is great. I appreciate the team for ability to use so great product.

  3. Cube says:

    What about OS X? I still run Android Studio on JDK 6 because of much better fonts rendering and Google even have explanation for that—http://tools.android.com/tech-docs/configuration/osx-jdk

  4. Pingback: Java Annotated Monthly – January 2016 | IntelliJ IDEA Blog

  5. singalen says:

    “Declaration access can be weaker” needs some tuning. For instance, it reports all the public methods when I’m developing a class that’s a part of a public API (that will be used in a different project). This can hint that I need an interface, but why forcing it?

  6. sernasan says:

    Users won’t be able to launch the IDE under a JDK older than Java 8. It means plugin developers now can use Java 8 features in their code. Where such information?

  7. Nigel Jacobs says:

    If I launch the IDE with Java 8, will I still be able to compile/run Java classes using earlier JDKs (i.e. 6) ?

    • Andrey Cheptsov says:

      Sure, you can use any JDK versions for your projects. The transition affects only the JDK used when running the IDE itself.

  8. Pingback: IntelliJ IDEA 16 EAP リリース – 今後はより早いリリースサイクルに | JetBrains ブログ

  9. Pingback: IntelliJ IDEA 16 EAP 144.2608 リリース | JetBrains ブログ

Leave a Reply

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