Now that we have a running project, let introduce jgitver on it, and compute automatically the project version.

Introducing jgitver on a Gradle project is as simple as adding the jgitver gradle plugin by adding the line (adapt version number if needed)

plugins {
    ...
    id 'fr.brouillard.oss.gradle.jgitver' version '0.6.0'
    ...
}

Let's do that automatically using sed:

sed -i "$((JL_LINE+1))i\ \ \ \ id 'fr.brouillard.oss.gradle.jgitver' version '0.6.0'" build.gradle

By building the project, Gradle will now download jgitver and its dependencies:

gradle build

Now verify that jgitver operates by checking again the project version
gradle --console=plain properties | grep -E '^version:.*'

jgitver gradle plugin also introduced a version task that ease to find current computed version:

gradle version

As you can see the project version is now overridden by jgitver to 0.0.0-0.

As we edited the build.gradle file to add the plugin, let's be clean and commit it. Wel'l then check the version again.

git commit -am "introduce jgitver plugin" && \ gradle version

Using no special configuration, project versioning starts with 0.0.0 and a distance qualifier is appended to the version.

Our project's version is now: 0.0.0-1

Now let's terminate this introduction with one of the main interesting feature of jgitver: tagging.

Let's consider that we are satisfied with the current state of our project and we want to release it using a defined 1.0.0 version.

For that you just need to create a tag git tag -a -m "release 1.0.0" 1.0.0

You can verify that the tag is there and that git HEAD is on the same commit than the tag git lg

Now Gradle project version calculated by jgitver should be 1.0.0
gradle version

jgitver should have hooked in the build and printed the following

~/demo-jgitver$ gradle version
> Task :version
Version: 1.0.0

BUILD SUCCESSFUL in 0s

Congratulations, you're now ready to publish the release 1.0.0 of your project to your preferred repository (Nexus, Maven Central, JCenter, ...).