Multi-Module Maven Projects

External

• Guide to Working with Multiple Modules https://maven.apache.org/guides/mini/guide-multiple-modules.html

Internal

• Maven Concepts

Overview

For guidelines on when it is appropriate to use modules, and when separate projects, see "When We Should Use Modules ?" section.

<project>
    ...
    <modules>
        <module>module1</module>
        <module>module2</module>
    </modules>
    ...
</project>

Each <module> element corresponds to a subdirectory of the top level project directory. Maven will look into these subdirectories for pom.xml files. Each module will have its own independent source hierarchy.

When We Should Use Modules?

Two major benefits of a multi-module project are that all the parts can be built with a single command, and Maven handles the correct build order.

Modules and Versions

Different modules of the same project can have different version.

Organizatorium

• The modules do not need to specify their <groupId>, as it is inherited from their parent, and thus redundant.