Menu
I have 3 maven projects
When i build each of the projects i have to go into each folder and run mvn clean install on each of the projects.
I have looked into multi module projects and most of the resources i see suggest that i have to make a change to the structure of my existing projects.
Is it possible to have a new project that will build each of the independent projects without me having to make any changes to anything in the existing project including their individual pom files?
I can probably achieve this by writing a simple batch file that builds every projects but is it possible using Maven?
654
As seen in the introduction to the POM, Maven supports project aggregation in addition to project inheritance. This section outlines how Maven processes projects with multiple modules, and how you can work with them more effectively.
POM Aggregator (Parent POM) Let's understand the structure of the multi-module application that we have created. Step 1: Create a Maven Project with the name spring-boot-multimodule. Step 2: Open the pom. xml (parent pom) file and change the packaging type jar to pom.
A multi-module project is built from an aggregator POM that manages a group of submodules. In most cases, the aggregator is located in the project's root directory and must have packaging of type pom. The submodules are regular Maven projects, and they can be built separately or through the aggregator POM.
Yes you can use Maven Profiles to manage this. Obviously you can tweak this approach to suit your needs however works best.
You're looking for Maven aggregation without inheritance. As shown in the referenced page, you just create a new POM whose packaging is "pom" and which has a list of "modules". A module is a relative path to another Maven project:
<project> ... <packaging>pom</packaging> ... <modules> <module>foo</module> <!-- module is in a subdirectory of this project --> <module>../bar</module> <!-- module is a sibling to this project --> <module>../../../other-projects/baz</module> <!-- somewhere else entirely --> </modules> </project> Default behavior when building such a pom--known as an "aggregator"--is to build all of the modules as if you'd executed Maven in each module directory with the same arguments.
120
If you add an aggregator project in the directory above the three projects that names them as modules (module name = subdirectory name), it will build them without needing any changes in their own POMs. They don't need to reference it as a parent.
37
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
