Deriving maven artifact version from git branch

Indeed, Maven can't change the version of it's own project in one run with other goals. On top of it, as far as I know, Maven doesn't support arbitrary properties in the <version> tag. Therefore, a separate execution is required to run a goal which will change the version of the POM. There are various plugins which can do it - for this case one might use the versions:set goal from versions plugin - http://mojo.codehaus.org/versions-maven-plugin/set-mojo.html

So, one might execute it as follows for example:

mvn versions:set -DgenerateBackupPoms=false -DnewVersion=$branch-SNAPSHOT

where the $branch variable has to contain current Git branch name; it can be extracted with git rev-parse, like this:

branch=$(git rev-parse --abbrev-ref HEAD)

But still, one needs to execute it somehow. You can do manually, but it is cumbersome. So, my guess is that indeed the most robust solution would be to approach this from Git side. That is - a Git hook. Here is the complete Git post-checkout hook which will do the job (same code as above with some filtering to run the hook only when the branch is checked out, not the individual files only):

#!/bin/bashecho 'Will change the version in pom.xml files...'# check if the checkout was to checkout a branchif [ $3 != '1' ]    then echo 'git checkout did not checkout a branch - quitting';exitfi# get current branch namebranch=$(git rev-parse --abbrev-ref HEAD)version=$branch-SNAPSHOT# run maven versions plugin to set new versionmvn versions:set -DgenerateBackupPoms=false -DnewVersion=$versionecho 'Changed version in pom.xml files to $version'

Put this content to the file PROJECTDIR\.git\hooks\post-checkout file. Note that the hook file should be executable to run it (chmod +x post-checkout).

Few notes about versions plugin - it is pretty flexible and supports many options and have few other goals which might be of help, depending on your project structure (do you use parent poms or not, do childs have their own versions or do they derive from parent, etc.). So, the hook above might be modified slightly to support you specific case by using other goals from versions plugin or by specifying additional parameters.

Pros:

• Robust
• No need to change anything in the pom.xml files themselves to make this work
• This "functionality" can be turned off simply by deactivating the hook (remove or make not executable) - again, no changes are required in the pom.xml

Cons:

• One can't enforce others to use a hook - it should be installed manually after the repo is cloned (or, you can provide a script to install the hook if supposed Git users are afraid of touching the stuff inside .git directory).

UPDATE

Hereafter is the more complicated version of the hook, which will not only set the version to the branch name, but will also preserve the suffix of the old version. For example, provided old version master-1.0-SNAPSHOT, switching to feature1 branch will change the version of the project to feature1-1.0-SNAPSHOT. This bash script suffers from few problems (requires branch names without dash symbol (-) in the name, and only takes the version of the root pom), but may give an idea of how the hook may be extended: given a mix of mvn and bash commands you can extract and update quite a lot of the information in the POM.

#!/bin/bashecho 'Will change the version in pom.xml files...'# check if the checkout was to checkout a branchif [ $3 != '1' ]    then echo 'git checkout did not checkout a branch - quitting';exitfi# get current branch namebranch=$(git rev-parse --abbrev-ref HEAD)# get current version of the top level pomcurrent_version=$(mvn help:evaluate -Dexpression=project.version | grep -v '\[.*')# extract version suffixsuffix=$(echo $current_version | cut -d \- -f 2)# build new versionversion=$branch-$suffix# run maven versions plugin to set new versionmvn versions:set -DgenerateBackupPoms=false -DnewVersion=$versionecho 'Changed version in pom.xml files to $version'

Sorry to revive this question and to post very lately another solution but it is possible indeed to change maven version dynamically and to use some git features, a little bit like git describe would do.

The project that does this is jgitver-maven-plugin (disclaimer; I am the author), it uses jgitver a jgit based library in order to derive maven project version from git information .

It is very easy to use as a maven extension

...  <build>      <extensions>          <extension>              <groupId>fr.brouillard.oss</groupId>              <artifactId>jgitver-maven-plugin</artifactId>              <version>0.1.0</version>          </extension>      </extensions>     ...  </build>...

The extension can also be used as a plugin extension, and then allows more configuration , for example in case you would not like to use SNAPSHOTS.See the project page for a description of full usage scenarios.

There is also a gradle plugin available that does more or less the same.

[edit 1]: answer to Thorbjørn Ravn Andersen comment

The plugin does not modify the original pom files or the build.gradle files.
For the maven plugin, modifications are done both in memory in the maven Object Model and written to a temporary file in temp directory. The calculation is based on the git metadata only (tags, commits, ...).
This non modification allows to not pollute the git history. WHen your are satisfied with a git commit, tag it git tag -a x.y.z and mvn deploy : that's all.
The version in your project files, is now useless and can be set to 0 for example.

As of today, and due to IDEA-155733 only recent EAP versions of IntelliJ work with the maven plugin.Eclipse & Netbeans have no problem.

Disclaimer: I am the author

My maven core extension will virtually set the version based on the current branch or tag. You can config custom version format patterns as you like.

https://github.com/qoomon/maven-branch-versioning-extension

Version Format Example