Multi-Module Maven Projects: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
Each <tt><module></tt> element corresponds to a ''subdirectory'' of the top level project directory. Maven will look into these subdirectories for <tt>pom.xml</tt> files. Each module will have its own independent source hierarchy. | Each <tt><module></tt> element corresponds to a ''subdirectory'' of the top level project directory. Maven will look into these subdirectories for <tt>pom.xml</tt> files. Each module will have its own independent source hierarchy. | ||
=The Reactor= | |||
Revision as of 17:03, 4 November 2016
External
- Guide to Working with Multiple Modules https://maven.apache.org/guides/mini/guide-multiple-modules.html
Internal
Overview
<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
Organizatorium
- The modules do not need to specify their <groupId>, as it is inherited from their parent, and thus redundant.