Multi-Module Maven Projects: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 12: | Line 12: | ||
For guidelines on when it is appropriate to use modules, and when separate projects, see "[[#When_We_Should_Use_Modules.3F|When We Should Use Modules ?]]" section. | For guidelines on when it is appropriate to use modules, and when separate projects, see "[[#When_We_Should_Use_Modules.3F|When We Should Use Modules ?]]" section. | ||
=The Reactor= | =The Reactor= | ||
Revision as of 17:24, 4 November 2016
External
- Guide to Working with Multiple Modules https://maven.apache.org/guides/mini/guide-multiple-modules.html
- A multi-module project http://books.sonatype.com/mvnex-book/reference/multimodule.html
Internal
Overview
For guidelines on when it is appropriate to use modules, and when separate projects, see "When We Should Use Modules ?" section.
The Reactor
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.
POM Structure
The Parent POM
A multi-module project is defined by a parent POM referencing one or more submodules. The essential elements are the packaging, which is of type "pom", and the list of modules.
...
<packaging>pom</packaging>
...
Organizatorium
- The modules do not need to specify their <groupId>, as it is inherited from their parent, and thus redundant.