Version 10.0.1 is finally there and includes various bug-fixes and improvements :-)
What's Changed
Dependencies used by the plugin
- #915: bump commons-io:commons-io from 2.21.0 to 2.22.0
- #933: bump org.jspecify:jspecify from 1.0.0 to 1.0.1
- #919: bump org.slf4j:slf4j-simple from 2.0.17 to 2.0.18 (test)
- bump git-commit-id-plugin-core from 6.2.0 to 6.2.1 (refs https://github.com/git-commit-id/git-commit-id-plugin-core/releases/tag/v6.2.1, fix CVE-2026-59638 by making use of org.bouncycastle:bcpkix-jdk18on 1.85)
Github Action
- #924: bump actions/cache from 5 to 6
- #923: bump actions/checkout from 6 to 7
- #935: bump actions/setup-java from 5 to 6
Maven Plugins used by the plugin
- #921: bump org.apache.maven.plugins:maven-site-plugin from 3.21.0 to 3.22.0
- #918: bump org.apache.maven.plugins:maven-enforcer-plugin from 3.6.2 to 3.6.3
- #925: bump org.apache.maven.plugins:maven-surefire-plugin from 3.5.5 to 3.5.6
- #927: bump org.jacoco:jacoco-maven-plugin from 0.8.14 to 0.8.15
- #928: bump org.apache.maven.plugins:maven-dependency-plugin from 3.10.0 to 3.11.0
- #930: bump org.sonatype.central:central-publishing-maven-plugin from 0.10.0 to 0.11.0
- #934: bump org.apache.maven.plugins:maven-jar-plugin from 3.5.0 to 3.5.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>10.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
Full Changelog: v10.0.0...v10.0.1