Try IntelliJ IDEA 14 EAP 138.1283.4 with Code Cleanup, Android Studio Beta Features and More

I bet you’ll agree with me that dealing with legacy code is not a pleasant task. Almost like cleaning up an old storage room full of dust and garbage. Even if you have powerful inspections that tell you what’s going wrong, you still have to run them manually and then apply quick-fixes one by one on every of the errors you have found. We don’t like mundane tasks like that, and that’s why in the new IntelliJ IDEA 14 EAP build we’re adding the new Code Cleanup feature that automatically fixes your code for you, in one click instead of dozen.

To use the feature, simply go to Analyse → Code Cleanup… menu. You’ll get a simple dialog where you specify the scope of project files that you want analyzed and fixed, and the inspection profile to use for that.

Screen Shot 2014-07-25 at 11.25.29

You can change the list of used inspections by clicking the button next to the inspection profile selector.

Screen Shot 2014-07-25 at 13.38.18

When you come across an corresponding issue in the editor, IntelliJ IDEA offers you to run the Code Cleanup over the entire file right from there.

Screen Shot 2014-07-25 at 11.52.45

And, of course, you will be prompted to clean your code up before committing changes to a VCS.

Screen Shot 2014-07-25 at 11.31.01

In addition to the Code Cleanup option IntelliJ IDEA 14 EAP build also includes features merged from Android Studio Beta, among other enhancements and bugfixes.

Feel free to share your feedback here, or on our discussion forum, and don’t forget to submit any problems you find to the issue tracker.

Develop with Pleasure!

This entry was posted in New Features and tagged , , , . Bookmark the permalink.

7 Responses to Try IntelliJ IDEA 14 EAP 138.1283.4 with Code Cleanup, Android Studio Beta Features and More

  1. Will says:

    I can no longer use python plugin after this update, any ideas?

  2. Someone says:

    Relating to IntelliJ IDEA 13: Is there any way to install IntelliJ IDEA 12’s Darcula theme?

    13’s Darcula is really really awful and immensely confusing. I wouldn’t like to get stuck on 12, only for a regression on the theme…

  3. Chris says:

    Been using and loving IntelliJ since at least the 4.x version, but I won’t pay for an upgrade to 14 until you guys release a non-beta version of 13 first. Obviously 13.1.4 isn’t that, since it’s broken for Grails project creation. And the earlier 13.x versions lock up X-Windows on occasion and are very consistent when it comes to saving files on losing focus.

    It’s the first time I ever regretted an IntelliJ upgrade. And that seems to be a pretty common sentiment online. Please fix the 13.x product line so that I’ll have enough faith to shell out another $100 this year.

  4. Pingback: Kotlin M13 is out! | Kotlin Blog

  5. Abdellah says:

    Any idea about the equivalent way using Android Studio command line

  6. Pingback: IntelliJ IDEA 16 EAP新ビルドのリリース – デバッガの改善とGitワークツリーのサポート | JetBrains ブログ

Leave a Reply

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