IntelliJ IDEA 11.1 EAP begins

Dmitry Jemerov

We’re happy to announce the beginning of the Early Access Preview program for the next feature update of IntelliJ IDEA, version 11.1. This version will be released in a couple of months and will be a free upgrade for existing users of IntelliJ IDEA 11.

A brief list of features already implemented in the new EAP includes:

  • Continued work on UI changes (Project View, run/debug toolwindows UI redesigned);
  • Subversion 1.7 support (work in progress);
  • Performance improvements in Git and Perforce integration;
  • New Coverage view;
  • New tree-based File Structure Popup;
  • Improved popup for controlling Git branches (checkout, compare, delete, multi-root support);
  • Highlighting of unused public members in Groovy code;
  • Extract Closure refactoring for Groovy;
  • New Flex project structure UI (work in progress);
  • Spring support improvements;
  • Gradle project synchronization support (work in progress);
  • Android lint tool integration;
  • Magic Constant inspection and code completion;
  • Possibility to run JUnit or TestNG tests for any selection of classes or methods

In the coming weeks we plan to publish blog posts describing each of the new features in more detail. And for the time being, you can download IntelliJ IDEA 11.1 EAP try them out for yourself.

As always, your feedback is welcome in the issue tracker.

Note that this EAP cycle does not include 30-day time-limited licenses in each build. In order to use these builds, you need to have a valid license for IntelliJ IDEA 11.

Comments below can no longer be edited.

13 Responses to IntelliJ IDEA 11.1 EAP begins

  1. benjamin says:

    February 8, 2012

    since I’m heavily working on idea projects with multiple git roots, I can’t wait to see those features in action. 🙂

  2. Jonathan Toland says:

    February 8, 2012

    My license for 11 (upgraded from 10) is denied by this EAP. Licensing bug?

  3. Steve Holmes says:

    February 8, 2012

    Will the Groovy optimize imports bugfixes be included?

  4. yole says:

    February 8, 2012

    Please re-enter your IDEA 11 license key, it will be accepted. Sorry for inconvenience, will be fixed in next EAP.

  5. Jonathan Toland says:

    February 8, 2012

    Worked like a charm thx a million!

  6. Kim says:

    February 8, 2012

    Looking forward to improved Spring and Gradle support!

  7. Peter Gromov says:

    February 8, 2012

    Steve, which bugfixes?

  8. canab says:

    February 9, 2012

    Flex sdks configured in 11 are not recognizing by 11.1 and vice versa. It makes chaos in sdk names. I thing It would be more convenient to store 11.1 configuration in a separate folder (%USERPROFILE%.IntelliJIdea11.1) and do export settings from the previous version.

    And what is the reason to put dependencies into child nodes of module (in a project configuration).

    PS. Captcha recognizing is a nightmare 🙂

  9. Alexander Doroshko says:

    February 9, 2012

    @canab We never change global IDEA config folder when performing minor IDEA version update. Chaos will end when you’ll finally decide to stay with either IDEA 11.0 or IDEA 11.1. You’ll need to cleanup incompatible SDKs once.
    Flex dependencies are now configured at build configuration level because you may have several absolutely different build configurations for one module. For example you can use the same module code base to build SWFs for different target players or for web, desktop and mobile platform or with different SDKs. You can select build configuration that should be used for current source files highlighting in the respective widget in the status bar.

  10. canab says:

    February 9, 2012

    Thanks for the detailed response.

    > Chaos will end when you’ll finally decide to stay with either IDEA 11.0 or IDEA 11.1

    Yes, but what about several projects that are being develop in a different versions? (11/11.1) It is not possible migrate all of them in a one moment because of some people/teams are not able to migrate.

    It is a common situation that one developer supports several projects in a different versions of IDE. Now, when 11 and 11.1 have significant amount of incompatible settings it would be quite problematic migrate and support other projects.

  11. Alexander Doroshko says:

    February 9, 2012

    @canab I think seeing several SDKs that are incompatible with current IDEA version is not a big problem. But nobody can prevent you from using different global config folders for different versions of IDEA. Path to config/system folders is configurable:

  12. canab says:

    February 9, 2012

    @Alexander Doroshko Due to some specifics we have a lot of SDK and strong rules of naming them. That is why I was writing here. BTW, configurable folders location is a solution, thanks.

  13. Alexander Doroshko says:

    February 9, 2012

    @canab I hope new concept of Flex project setup allows to deal with your specifics. I’m ready to continue discussion at the forum:


Subscribe for updates