Multi-Module Maven Projects: Difference between revisions
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
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. | ||
<pre> | <pre> | ||
<project> | <project> |
Revision as of 17:07, 4 November 2016
External
- Guide to Working with Multiple Modules https://maven.apache.org/guides/mini/guide-multiple-modules.html
Internal
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.
The Reactor
When We Should Use Modules?
Modules and Versions
Organizatorium
- The modules do not need to specify their <groupId>, as it is inherited from their parent, and thus redundant.