Fork me on GitHub


This mojo is designed to get a unique build number for each time you build your project. So while your version may remain constant at 1.0-SNAPSHOT for many iterations until release, you will have a build number that can uniquely identify each build during that time. The build number is obtained from scm. You can then place that build number in metadata, which can be accessed from your app, if desired.

The mojo also has a couple of extra functions to ensure you get the proper build number. First, your local repository is checked to make sure it is up to date. Second, your local repository is automatically updated, so that you get the latest build number. Both these functions can be suppressed, if desired.

Optionally, you can configure this mojo to produce a revision based on a timestamp, or on a sequence, without requiring any interaction with an SCM system. Note that currently, supported SCMs are : subversion, git, mercurial, and perforce(using p4maven)

Goals Overview


Instructions on how to use the Build Number Maven Plugin can be found on the usage page.


Starting with version 3.0.0 of the plugin the default behaviour has been changed. If you define doCheck with true the plugin will really only check for modifications and will set the property buildIsTainted with the value tainted. If there are no modification this property will be set to ok.

If you like to fail the build as in previous versions you have to set the supplemental configuration failTheBuild to true and set doCheck to to true.