Releases · git-commit-id/git-commit-id-maven-plugin

Version 10.0.0 is finally there and includes various bug-fixes and improvements :-)

⚠️ This is a potentially breaking release. Read the release-notes carefully ⚠️

Potential Breaking changes:

The main key-aspects that might cause a breakage when migrating to the new version:

#913 / #914: Require Maven 3.9.0 [Maven 3.6.3 is EOL] ⚠️

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>10.0.0</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in #279 (comment)
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to #287 or #413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Full Changelog: v9.2.0...v10.0.0

Version 9.2.0 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

bump several plugins
- bump io.github.git-commit-id:git-commit-id-plugin-core from 6.1.5 to 6.2.0
  - replace org.eclipse.jgit.ssh.jsch with org.eclipse.jgit:org.eclipse.jgit.ssh.apache (see https://github.com/eclipse-jgit/jgit/blob/master/org.eclipse.jgit.ssh.jsch/README.md)
  - add org.bouncycastle:bcpkix-jdk18on version 1.81
  - remove joda-time:joda-time [replaced with Java 8+ Time API]
  - replace com.google.code.findbugs:jsr305 version 3.0.2 with org.jspecify:jspecify version 1.0.0
  - Full list: https://github.com/git-commit-id/git-commit-id-plugin-core/releases/tag/v6.2.0

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>9.2.0</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in #279 (comment)
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to #287 or #413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Full Changelog: v9.1.0...v9.2.0

@mharriger

Version 9.1.0 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

git-commit-id/git-commit-id-plugin-core#247 / #136 / #535: Add support for perModuleVersions (thanks @mharriger)
Extended testing support to Java 24, 25, and 26
Migrated from oss-parent to central-publishing-maven-plugin for deployment

bump several plugins
- bump io.github.git-commit-id:git-commit-id-plugin-core from 6.0.0 to 6.1.5
  - bump org.eclipse.jgit:org.eclipse.jgit from 6.10.0.202406032230-r to 6.10.1.202505221210-r
  - bump org.eclipse.jgit:org.eclipse.jgit.ssh.jsch from 6.10.0.202406032230-r to 6.10.1.202505221210-r
  - bump joda-time:joda-time from 2.14.0 to 2.14.1
  - bump org.yaml:snakeyaml from 2.4 to 2.6
  - Full list: https://github.com/git-commit-id/git-commit-id-plugin-core/releases/tag/v6.1.5
- bump commons-io:commons-io from 2.19.0 to 2.21.0 (scope test)
- bump org.junit.jupiter:* from 5.12.2 to 5.13.4 (scope test)
- bump org.mockito:mockito-core from 5.18.0 to 5.23.0 (scope test)
- bump org.assertj:assertj-core from 3.27.3 to 3.27.7 (scope test)
bump several maven plugins
- bump org.apache.maven.plugins:maven-antrun-plugin from 3.1.0 to 3.2.0
- bump org.apache.maven.plugins:maven-assembly-plugin from 3.7.1 to 3.8.0
- bump org.apache.maven.plugins:maven-clean-plugin from 3.4.1 to 3.5.0
- bump org.apache.maven.plugins:maven-compiler-plugin from 3.14.0 to 3.15.0
- bump org.apache.maven.plugins:maven-dependency-plugin from 3.8.1 to 3.10.0
- bump org.apache.maven.plugins:maven-enforcer-plugin from 3.5.0 to 3.6.2
- bump org.apache.maven.plugins:maven-gpg-plugin from 3.2.7 to 3.2.8
- bump org.apache.maven.plugins:maven-jar-plugin from 3.4.2 to 3.5.0
- bump org.apache.maven.plugins:maven-javadoc-plugin from 3.11.2 to 3.12.0
- bump org.apache.maven.plugins:maven-plugin-plugin from 3.15.1 to 3.15.2
- bump org.apache.maven.plugins:maven-release-plugin from 3.1.1 to 3.3.1
- bump org.apache.maven.plugins:maven-resources-plugin from 3.3.1 to 3.5.0
- bump org.apache.maven.plugins:maven-source-plugin from 3.3.1 to 3.4.0
- bump org.apache.maven.plugins:maven-surefire-plugin from 3.5.3 to 3.5.5
- bump org.codehaus.mojo:versions-maven-plugin from 2.18.0 to 2.21.0
- bump org.codehaus.mojo:exec-maven-plugin from 3.5.0 to 3.6.3
- bump org.jacoco:jacoco-maven-plugin from 0.8.13 to 0.8.14
- bump org.apache.maven.plugin-tools:maven-plugin-annotations from 3.15.1 to 3.15.2

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>9.1.0</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in #279 (comment)
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to #287 or #413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Full Changelog: v9.0.2...v9.1.0

Version 9.0.2 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

general changes
- #833: Update docs
bump several plugins
- bump io.github.git-commit-id:git-commit-id-plugin-core from 6.0.0-rc.8 to 6.0.0
  - Includes #847: Add support for Github Actions build number
  - Refer to https://github.com/git-commit-id/git-commit-id-plugin-core/releases/tag/v6.0.0 for a full-changelog
- bump org.junit.jupiter:* from 5.10.2 to 5.12.2 (scope test)
- bump org.mockito:mockito-core from 5.12.0 to 5.18.0 (scope test)
- bump org.assertj:assertj-core from 3.26.0 to 3.27.3 (scope test)
- bump commons-io:commons-io from 2.16.1 to 2.19.0 (scope test)
- bump org.slf4j:slf4j-simple from 2.0.13 to 2.0.17 (scope test)
bump several maven plugins
- bump org.apache.maven.plugins:maven-plugin-plugin from 3.13.1 to 3.15.1
- bump org.apache.maven.plugins:maven-dependency-plugin from 3.7.1 to 3.8.1
- bump org.apache.maven.plugins:maven-release-plugin from 3.1.0 to 3.1.1
- bump org.apache.maven.plugins:maven-compiler-plugin from 3.13.0 to 3.14.0
- bump org.apache.maven.plugins:maven-gpg-plugin from 3.2.4 to 3.2.7
- bump org.apache.maven.plugins:maven-clean-plugin from 3.4.0 to 3.4.1
- bump org.apache.maven.plugins:maven-jar-plugin from 3.4.1 to 3.4.2
- bump org.apache.maven.plugins:maven-surefire-plugin from 3.3.0 to 3.5.3
- bump org.apache.maven.plugins:maven-install-plugin from 3.1.2 to 3.1.4
- bump org.apache.maven.plugins:maven-deploy-plugin from 3.1.2 to 3.1.4
- bump org.apache.maven.plugins:maven-site-plugin from 3.12.1 to 3.21.0
- bump org.apache.maven.plugins:maven-javadoc-plugin from 3.7.0 to 3.11.2
- bump org.apache.maven.plugins:maven-release-plugin from 3.1.0 to 3.1.1

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>9.0.2</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in #279 (comment)
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to #287 or #413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Full Changelog: v9.0.1...v9.0.2

Version 9.0.1 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

#754 / #760: Fix an issue where empty git.properties had been generated in submodules when injectAllReactorProjects=true
bump several maven plugins
- bump org.apache.maven.plugins:maven-checkstyle-plugin from 3.3.1 to 3.4.0
- bump org.apache.maven.plugins:maven-release-plugin from 3.0.1 to 3.1.0
- bump org.apache.maven.plugins:maven-surefire-plugin from 3.2.5 to 3.3.0
- bump org.apache.maven.plugins:maven-clean-plugin from 3.3.2 to 3.4.0
- bump org.apache.maven.plugins:maven-dependency-plugin from 3.6.1 to 3.7.1

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>9.0.1</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in #279 (comment)
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to #287 or #413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 9.0.0 is finally there and includes various bug-fixes and improvements :-)

⚠️ This is a potentially breaking release. Read the release-notes carefully ⚠️

Potential Breaking changes:

The main key-aspects that might cause a breakage when migrating to the new version:

#737 / #710: Require Maven 3.6.3 ⚠️

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

Use javac --release instead of -source & -target
Delete BigDiffTest
bump several maven plugins
- bump org.apache.maven.plugins:maven-assembly-plugin from 3.7.0 to 3.7.1
- bump org.apache.maven.plugins:maven-gpg-plugin from 3.2.0 to 3.2.4
- bump maven-plugin-plugin.version from 3.11.0 to 3.12.0
- bump org.apache.maven.plugins:maven-source-plugin from 3.3.0 to 3.3.1
- bump org.jacoco:jacoco-maven-plugin from 0.8.11 to 0.8.12
- bump org.apache.maven.plugins:maven-compiler-plugin from 3.12.1 to 3.13.0
- bump org.apache.maven.plugins:maven-jar-plugin from 3.3.0 to 3.4.1
- bump org.apache.maven.plugins:maven-install-plugin from 3.1.1 to 3.1.2
- bump org.apache.maven.plugins:maven-deploy-plugin from 3.1.1 to 3.1.2
- bump maven-plugin-plugin.version from 3.12.0 to 3.13.0
- bump org.codehaus.mojo:exec-maven-plugin from 3.2.0 to 3.3.0
- bump maven-plugin-plugin.version from 3.13.0 to 3.13.1
- bump org.apache.maven.plugins:maven-javadoc-plugin from 3.6.3 to 3.7.0
- bump org.apache.maven.plugins:maven-enforcer-plugin from 3.4.1 to 3.5.0
bump several dependencies

bump commons-io:commons-io from 2.15.1 to 2.16.1
bump org.slf4j:slf4j-simple from 2.0.12 to 2.0.13 (tests)
bump org.mockito:mockito-core from 5.11.0 to 5.12.0 (tests)
bump org.assertj:assertj-core from 3.25.3 to 3.26.0 (tests)

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>9.0.0</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in #279 (comment)
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to #287 or #413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 8.0.2 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

bump jakarta.xml.bind:jakarta.xml.bind-api from 4.0.1 to 4.0.2
bump org.mockito:mockito-core from 5.10.0 to 5.11.0
#718/#721: replace junit:junit:4.13.2:test with org.junit.jupiter:junit-jupiter-*:5.10.2:test
#717/#720: update org.sonatype.plexus:plexus-build-api:0.0.7 to org.codehaus.plexus:plexus-build-api:1.2.0
bump org.apache.maven.plugins:maven-gpg-plugin from 3.1.0 to 3.2.0
bump org.apache.maven.plugins:maven-assembly-plugin from 3.6.0 to 3.7.0
#717: Update maven-plugin-api.version from 3.9.2 to 3.9.6

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>8.0.2</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in #279 (comment)
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to #287 or #413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 8.0.1 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

make use of git-commit-id-plugin-core:6.0.0-rc.8
- downgrade jgit.version from 6.8.0.202311291450-r to 6.7.0.202309050840-r (#712)

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>8.0.1</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in #279 (comment)
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to #287 or #413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 8.0.0 is finally there and includes various bug-fixes and improvements :-)

⚠️ This is a potentially breaking release. Read the release-notes carefully ⚠️

Potential Breaking changes:

The main key-aspects that might cause a breakage when migrating to the new version:

#674/#699: change default timeformat/dateformat from RFC822 to ISO 8601 to support maven's reproducible build feature ⚠️

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

#701/#705: Fix an issue where running with submodules using the native git executable was causing a fatal: this operation must be run in a work tree
#700: Only injects properties into every reactor project once
#683: [pom] Add encoding to pom and correct maven xsd location
make use of git-commit-id-plugin-core:6.0.0-rc.7 (move the GitDirLocator related logic to git-commit-id-plugin-core)
- bump org.eclipse.parsson:parsson from 1.1.4 to 1.1.5
- bump org.mockito:mockito-core from 5.6.0 to 5.10.0
- bump commons-io:commons-io from 2.14.0 to 2.15.1
- bump jgit.version from 6.7.0.202309050840-r to 6.8.0.202311291450-r
- bump jakarta.json:jakarta.json-api from 2.1.2 to 2.1.3
- bump org.yaml:snakeyaml from 2.0 to 2.2
- bump org.assertj:assertj-core from 3.24.2 to 3.25.3
- bump org.slf4j:slf4j-simple from 2.0.9 to 2.0.12
- bump joda-time:joda-time from 2.12.5 to 2.12.7
bump several maven plugins
- bump maven-plugin-plugin.version from 3.9.0 to 3.11.0
- bump org.apache.maven.plugins:maven-dependency-plugin from 3.6.0 to 3.6.1
- bump org.apache.maven.plugins:maven-surefire-plugin from 3.1.2 to 3.2.5
- bump org.apache.maven.plugins:maven-checkstyle-plugin from 3.3.0 to 3.3.1
- bump org.apache.maven.plugins:maven-clean-plugin from 3.3.1 to 3.3.2
- bump org.apache.maven.plugins:maven-javadoc-plugin from 3.6.0 to 3.6.3
- bump org.codehaus.mojo:exec-maven-plugin from 3.1.0 to 3.2.0
- bump org.jacoco:jacoco-maven-plugin from 0.8.10 to 0.8.11
- bump org.apache.maven.plugins:maven-compiler-plugin from 3.11.0 to 3.12.1
bump several dependencies
- bump commons-io:commons-io from 2.14.0 to 2.15.1
- bump org.mockito:mockito-core from 5.6.0 to 5.10.0
- bump jakarta.xml.bind:jakarta.xml.bind-api from 2.3.3 to 4.0.1
- bump org.slf4j:slf4j-simple from 2.0.9 to 2.0.12
- bump org.assertj:assertj-core from 3.24.2 to 3.25.3
- bump com.puppycrawl.tools:checkstyle from 8.25 to 10.13.0
- bump actions/setup-java from 3 to 4
- bump actions/cache from 3 to 4

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>8.0.0</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in #279 (comment)
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to #287 or #413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 7.0.0 is finally there and includes various bug-fixes and improvements :-)

⚠️ This is a potentially breaking release. Read the release-notes carefully ⚠️

Potential Breaking changes:

The main key-aspects that might cause a breakage when migrating to the new version:

Drop support for Maven 3.1.0-alpha-1 ⚠️
- minimal required maven version is now Maven 3.2.5 (to support Maven 4.0.0)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

#639 / #642: Resolve worktree .git files to repository .git directory
Update several plugins
- updated git-commit-id-plugin-core from 6.0.0-rc.5 to 6.0.0-rc.6, that update brings
  - git-commit-id/git-commit-id-plugin-core#57: Stop relying on javax.json 1.1.4
    - the dependency for javax.json:javax.json-api:1.1.4 was replaced with jakarta.json:jakarta.json-api:2.1.2
    - the dependency for org.glassfish:javax.json:1.1.4 was replaced with org.eclipse.parsson:parsson:1.1.4
  - bump jgit from 6.5.0.202303070854-r to 6.7.0.202309050840-r
  - bump commons-io:commons-io from 2.11.0 to 2.14.0
  - bump org.slf4j:slf4j-simple from 2.0.7 to 2.0.9
- bump several maven plugins
  - bump maven-plugin-api from 3.1.0-alpha-1 to 3.9.2
  - bump maven-plugin-plugin from 3.6.0 to 3.9.0
  - bump maven-assembly-plugin from 3.4.2 to 3.6.0
  - bump maven-dependency-plugin from 3.5.0 to 3.6.0
  - bump maven-release-plugin from 3.0.0-M7 to 3.0.1
  - bump maven-enforcer-plugin from 3.2.1 to 3.4.1
  - bump maven-compiler-plugin from 3.8.1 to 3.11.0
  - bump maven-gpg-plugin from 3.1.0
  - bump maven-clean-plugin from 3.1.0 to 3.3.1
  - bump maven-resources-plugin from 3.1.0 to 3.3.1
  - bump maven-jar-plugin from 3.2.0 to 3.3.0
  - bump maven-surefire-plugin from 2.22.2 to 3.1.2
  - bump maven-install-plugin from 2.5.2 to 3.1.1
  - bump maven-javadoc-plugin from 3.2.0 to 3.6.0
  - bump maven-source-plugin from 3.2.1 to 3.3.0
- Bump or replace various plugins for testing
  - bump commons-io:commons-io from 2.11.0 to 2.14.0 (test dependency)
  - bump org.slf4j:slf4j-simple from 2.0.7 to 2.0.9 (test dependency)
  - replace org.eluder.coveralls:coveralls-maven-plugin:4.3.0 with io.jsonwebtoken.coveralls:coveralls-maven-plugin:4.4.1 (test dependency)

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>7.0.0</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in #279 (comment)
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to #287 or #413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Releases: git-commit-id/git-commit-id-maven-plugin

Version 10.0.0

Potential Breaking changes:

Getting the latest release

Getting the latest snapshot (build automatically)

Known Issues / Limitations:

Reporting Problems

Uh oh!

Version 9.2.0

New Features / Bug-Fixes:

Getting the latest release

Getting the latest snapshot (build automatically)

Known Issues / Limitations:

Reporting Problems

Uh oh!

Version 9.1.0

New Features / Bug-Fixes:

Getting the latest release

Getting the latest snapshot (build automatically)

Known Issues / Limitations:

Reporting Problems

Contributors

Uh oh!

Version 9.0.2

New Features / Bug-Fixes:

Getting the latest release

Getting the latest snapshot (build automatically)

Known Issues / Limitations:

Reporting Problems

Uh oh!

Version 9.0.1

New Features / Bug-Fixes:

Getting the latest release

Getting the latest snapshot (build automatically)

Known Issues / Limitations:

Reporting Problems

Uh oh!

Version 9.0.0

Potential Breaking changes:

New Features / Bug-Fixes:

Getting the latest release

Getting the latest snapshot (build automatically)

Known Issues / Limitations:

Reporting Problems

Uh oh!

Version 8.0.2

New Features / Bug-Fixes:

Getting the latest release

Getting the latest snapshot (build automatically)

Known Issues / Limitations:

Reporting Problems

Uh oh!

Version 8.0.1

New Features / Bug-Fixes:

Getting the latest release

Getting the latest snapshot (build automatically)

Known Issues / Limitations:

Reporting Problems

Uh oh!

Version 8.0.0

Potential Breaking changes:

New Features / Bug-Fixes:

Getting the latest release

Getting the latest snapshot (build automatically)

Known Issues / Limitations:

Reporting Problems

Uh oh!

Version 7.0.0

Potential Breaking changes:

New Features / Bug-Fixes:

Getting the latest release

Getting the latest snapshot (build automatically)

Known Issues / Limitations:

Reporting Problems

Uh oh!