Updating version numbers of modules in a multi-module Maven project

Question

I have a multi-module maven project  We intend to version all these modules together  But as of now I am ending up hard-coding version in each of the module pom xml as below     lt parent gt       lt artifactId gt xyz-application lt  artifactId gt       lt groupId gt com xyz lt  groupId gt       lt version gt 2 50 0 g lt  version gt   lt  parent gt   lt modelVersion gt 4 0 0 lt  modelVersion gt   lt groupId gt com xyz lt  groupId gt   lt artifactId gt xyz-Library lt  artifactId gt   lt version gt 2 50 0 g lt  version gt    and the main parent module has the below configuration   lt modelVersion gt 4 0 0 lt  modelVersion gt   lt groupId gt com xyz lt  groupId gt   lt artifactId gt xyz-application lt  artifactId gt   lt version gt 2 50 0 g lt  version gt   lt packaging gt pom lt  packaging gt

User · Answer

The given answer assumes that the project in question use project inheritance in addition to module aggregation. In fact those are distinct concepts:

https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance_vs_Project_Aggregation

Some projects may be an aggregation of modules, yet not have a parent-child relationship between aggregator POM and the aggregated modules. (There may be no parent-child relationship at all, or the child modules may use a separate POM altogether as the "parent".) In these situations the given answer will not work.

After much reading and experimentation, it turns out there is a way to use the Versions Maven Plugin to update not only the aggregator POM but also all aggregated modules as well; it is the processAllModules option. The following command must be done in the directory of the aggregator project:

mvn versions:set -DnewVersion=2.50.1-SNAPSHOT -DprocessAllModules

The Versions Maven Plugin will not only update the versions of all contained modules, it will also update inter-module dependencies!!!! This is a huge win and will save a lot of time and prevent all sorts of problems.

Of course don't forget to commit the changes in all modules, which you can also do with the same switch:

mvn versions:commit -DprocessAllModules

You may decide to dispense with the backup POMS altogether and do everything in one command:

mvn versions:set -DnewVersion=2.50.1-SNAPSHOT -DprocessAllModules -DgenerateBackupPoms=false

User · Answer

I was looking for this   lt properties gt       lt maven compiler target gt 1 8 lt  maven compiler target gt       lt maven compiler source gt 1 8 lt  maven compiler source gt   lt  properties gt

User · Answer

To update main pom xml and parent version on submodules   mvn versions set -DnewVersion 1 3 0-SNAPSHOT -N versions update-child-modules -DgenerateBackupPoms false

User · Answer

You may want to look into Maven release plugin s release update-versions goal  It will update the parent s version as well as all the modules under it     Update  Please note that the above is the release plugin  If you are not releasing  you may want to use versions set  mvn versions set -DnewVersion 1 2 3-SNAPSHOT

User · Answer

Use versions set from the versions-maven plugin   mvn versions set -DnewVersion 2 50 1-SNAPSHOT   It will adjust all pom versions  parent versions and dependency versions in a multi-module project   If you made a mistake  do  mvn versions revert   afterwards  or  mvn versions commit   if you re happy with the results     Note  this solution assumes that all modules use the aggregate pom as parent pom also  a scenario that was considered standard at the time of this answer  If that is not the case  go for Garret Wilson s answer

User · Answer

If you want to fully automate the process  i e  you want to increment the version number without having to know what the current version number is   you can do this   mvn build-helper parse-version versions set -DnewVersion    parsedVersion majorVersion     parsedVersion minorVersion     parsedVersion nextIncrementalVersion  versions commit

User · Answer

I encourage you to read the Maven Book about multi-module  reactor  builds    I meant in particular the following    lt parent gt       lt artifactId gt xyz-application lt  artifactId gt       lt groupId gt com xyz lt  groupId gt       lt version gt 2 50 0 g lt  version gt   lt  parent gt   lt modelVersion gt 4 0 0 lt  modelVersion gt   lt groupId gt com xyz lt  groupId gt   lt artifactId gt xyz-Library lt  artifactId gt   lt version gt 2 50 0 g lt  version gt    should be changed into  Here take care about the not defined version only in parent part it is defined    lt modelVersion gt 4 0 0 lt  modelVersion gt    lt parent gt       lt artifactId gt xyz-application lt  artifactId gt       lt groupId gt com xyz lt  groupId gt       lt version gt 2 50 0 g lt  version gt   lt  parent gt   lt groupId gt com xyz lt  groupId gt   lt artifactId gt xyz-Library lt  artifactId gt    This is a better link

User · Answer

the easiest way is to change version in every pom xml to arbitrary version  then check that dependency management to use the correct version of the module used in this module  for example  if u want increase versioning for a tow module project u must do like flowing   in childe module         lt parent gt          lt artifactId gt A-application lt  artifactId gt          lt groupId gt com A lt  groupId gt          lt version gt new-version lt  version gt       lt  parent gt    and in parent module     lt groupId gt com A lt  groupId gt   lt artifactId gt A-application lt  artifactId gt   lt version gt new-version lt  version gt

User · Answer

versions update-child-modules sounds like what you re looking for   You could do versions set as mentioned  but this is a light-weight way to update the parent version numbers   For the child modules  it s my opinion that you should remove the  lt version gt  definitions  since they will inherit the parent module s version number

User · Answer

The solution given above worked for us as well for a long time  mvn versions set -DnewVersion 2 50 1-SNAPSHOT  However it stopped working yesterday  and we found it due to a recent bug in a the versions-maven-plugin Our  temporary  workaround was to change the parent pom xml file as follows  --- jackrabbit oak trunk oak-parent pom xml 2020 08 13 13 43 11 1880829     jackrabbit oak trunk oak-parent pom xml 2020 08 13 15 17 59 1880830    -329 6  329 13                lt artifactId gt spotbugs-maven-plugin lt  artifactId gt              lt version gt 3 1 11 lt  version gt            lt  plugin gt                      lt plugin gt              lt groupId gt org codehaus mojo lt  groupId gt              lt artifactId gt versions-maven-plugin lt  artifactId gt              lt version gt 2 7 lt  version gt            lt  plugin gt

User · Answer

The best way is  since you intend to bundle your modules together  you can specify  lt dependencyManagement gt  tag in outer most pom xml  parent module  direct under  lt project gt  tag  It controls the version and group name  In your individual module  you just need to specify the  lt artifactId gt  tag in your pom xml  It will take the version from parent file

[maven] Updating version numbers of modules in a multi-module Maven project

Examples related to maven