Early Access Program

IntelliJ IDEA 2017.3 EAP: Grouping modules according to their qualified names and more

Great news! The fresh IntelliJ IDEA 2017.3 EAP build is out! In this EAP build you will find notable features and very important bugfixes.

Last week Java 9 was released, and it brings the module concept to the Java platform – the project known as Jigsaw. Project Jigsaw aims to make it easier for developers to build and maintain large applications. The new concept encourages you to modularize your application. IntelliJ IDEA 2017.3 provides different features to support Java 9. You can learn more about Java 9 support in IntelliJ IDEA in this blogpost.

And with this new EAP, we expand the support for this with the new method of module organization – grouping modules according to their qualified names.

Up until now the IDE only offered one way to organize modules – module groups. There are several problems with such an approach. First of all, module names should be unique, over all the modules in a project. Also if you want to use the same module in different projects, you need to specify the module group for this module, in each project, because a module groups configuration stored in the project configuration, not *.iml files.

Screen Shot 2017-09-28 at 12.31.10

In this new EAP, IntelliJ IDEA can also use qualified names to organize modules. In the IntelliJ IDEA 2017.3 EAP build, grouping by qualified module names will be enabled by default if there are no module groups configured in your current project.

If the Flatten Module option is off, modules are shown as a hierarchy. If the Flatten Module option is on, modules appear at the same level.

Screen Shot 2017-09-28 at 08.19.59

Full release notes are available here.

We are currently working to enhance our support for Java EE 8 and CDI 2.0. Check out the new features in this EAP:

  • Support for async events.
  • Support for dynamic beans (CDI extensions).
  • Navigation from disposer methods to their producers.
  • New inspection: disposer methods without corresponding producers.
  • Support for implicit archives (without beans.xml).
  • Support for new built-in classes: RequestContextController and InterceptionFactory.

More details are coming soon in a separate blog post. Stay tuned!

We’re eager to know what do you think about new IntelliJ IDEA 2017.3 EAP. Please download it and share your feedback with us via comments, issue tracker or twitter.

Happy developing!


Comments below can no longer be edited.

8 Responses to IntelliJ IDEA 2017.3 EAP: Grouping modules according to their qualified names and more

  1. Avatar

    Simon Billingsley says:

    December 4, 2017

    Hello, I have just upgraded to IntelliJ 2017.3 from 2017.2 and I see this feature being used.
    Unfortunately I want to turn it off – is there a setting for this?
    I see both non-grouped and grouped modules in the same tree and it is confusing, and when I select a module in the non-grouped tree it jumps to the equivalent module in the grouped version.
    Also, the Maven Helper plugin does not build a module group, it can only work on a module (and its children, which is what I am trying to do).
    Thanks, Simon.

  2. Avatar

    Sprela Cart says:

    December 11, 2017

    After updating to 2017.3 I just tried to setup a new project containing a lot of modules (>30). My modules are organized by directories, which means I want to group all modules within a certain directory. Before 2017.3 this was quite easy by creating module groups and moving the modules to the appropriate group. Now, with 2017.3 it is not possible (for new projects) to group modules this way anymore. Even worse, there is no grouping at all: I have now an un-structured list of over 30 modules.

    How can I enable the old module grouping behaviour?

    • Avatar

      Bogumił says:

      December 14, 2017

      Its a nightmare:/ maybe someone will release plugin with this missing feature:/

  3. Avatar

    Cristian M. Castro says:

    December 14, 2017

    Please revert the old module grouping, this si very bad for us who have multiple modules.

  4. Avatar

    Oded Buchbinder says:

    January 16, 2018

    There is a way to remove the module from the group
    Right click the group and select remove module from group

  5. Avatar

    Mike says:

    February 27, 2018

    Guys – your module-grouping-system is totally broken. On every Gradle refresh the grouping is wiped out. It’s almost unusable. It annoys me everyday at least 2 or 3 times. This bug is open now for almost 2 years!!!! https://youtrack.jetbrains.com/issue/IDEA-153496

  6. Avatar

    Lars says:

    December 2, 2018

    This new grouping feature is not helpful at all for me. My use case is very simple:
    I want to import a nested multi-module Maven project into IntelliJIDEA and I want the module tree to reflect the directory structure or (maven module tree) without duplicates.
    This does not work since 2017.3.

Discover more