Maven Project Version Handling

Last update: 2022-07-08
  • Created for:
  • Admin

Learn how Maven handles project versioning in Cloud Manager.

How Maven Handles Project Versions

For staging and production deployments, Cloud Manager generates a unique, incrementing version.

This version is seen on the pipeline execution details page as well as the activity page. When a build is run, the Maven project is updated to use this version and a tag is created in the git repository with that version as its name.

If the original project version meets certain criteria, the updated Maven project version will merge both the original project version and the Cloud Manager generated version. The tag, however, always uses the generated version. For this merging to occur, the original project version must be formed with exactly three version segments, for example, 1.0.0 or 1.2.3, but not 1.0 or 1, and the original version must not end in -SNAPSHOT.


This original project version value must be statically set in the <version> element of the top-level pom.xml file in the git repository branch.

If the original version meets these criteria then the generated version will be appended to the original version as a new version segment. The generated version will also be slightly modified to include proper sorting and version handling. For example, assuming a generated version of 2019.926.121356.0000020490:

Version Version in pom.xml Comment
1.0.0 Properly formed original version
1.0.0-SNAPSHOT 2019.926.121356.0000020490 Snapshot version, overwritten
1 2019.926.121356.0000020490 Incomplete version, overwritten

Regardless of whether or not the original version was incorporated into the Cloud Manager-initialized version, the original version is available as a Maven property with the name cloudManagerOriginalVersion.

On this page