
Maven plugin which includes build-time git repository information into an POJO / *.properties). Make your apps tell you which version exactly they were built from! Priceless in large distributed deployments... :-)
Repo git-commit-id/git-commit-id-maven-plugin, read from GitHub 20 h ago. git-commit-id has not joined Take My Repo.
Version 10.0.1 is finally there and includes various bug-fixes and improvements :-)
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>
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.
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 workaroundsIf you find any problem with this plugin, feel free to report it here
Full Changelog: v10.0.0...v10.0.1
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 ⚠️
The main key-aspects that might cause a breakage when migrating to the new version:
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>
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.
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 workaroundsIf 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 :-)
The main key-aspects that have been improved or being worked on are the following:
io.github.git-commit-id:git-commit-id-plugin-core from 6.1.5 to 6.2.0
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)org.bouncycastle:bcpkix-jdk18on version 1.81joda-time:joda-time [replaced with Java 8+ Time API]com.google.code.findbugs:jsr305 version 3.0.2 with org.jspecify:jspecify version 1.0.0The 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>
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.
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 workaroundsIf you find any problem with this plugin, feel free to report it here
Full Changelog: v9.1.0...v9.2.0
Version 9.1.0 is finally there and includes various bug-fixes and improvements :-)
The main key-aspects that have been improved or being worked on are the following:
io.github.git-commit-id:git-commit-id-plugin-core from 6.0.0 to 6.1.5
org.eclipse.jgit:org.eclipse.jgit from 6.10.0.202406032230-r to 6.10.1.202505221210-rorg.eclipse.jgit:org.eclipse.jgit.ssh.jsch from 6.10.0.202406032230-r to 6.10.1.202505221210-rjoda-time:joda-time from 2.14.0 to 2.14.1org.yaml:snakeyaml from 2.4 to 2.6commons-io:commons-io from 2.19.0 to 2.21.0 (scope test)org.junit.jupiter:* from 5.12.2 to 5.13.4 (scope test)org.mockito:mockito-core from 5.18.0 to 5.23.0 (scope test)org.assertj:assertj-core from 3.27.3 to 3.27.7 (scope test)org.apache.maven.plugins:maven-antrun-plugin from 3.1.0 to 3.2.0org.apache.maven.plugins:maven-assembly-plugin from 3.7.1 to 3.8.0org.apache.maven.plugins:maven-clean-plugin from 3.4.1 to 3.5.0org.apache.maven.plugins:maven-compiler-plugin from 3.14.0 to 3.15.0org.apache.maven.plugins:maven-dependency-plugin from 3.8.1 to 3.10.0org.apache.maven.plugins:maven-enforcer-plugin from 3.5.0 to 3.6.2org.apache.maven.plugins:maven-gpg-plugin from 3.2.7 to 3.2.8org.apache.maven.plugins:maven-jar-plugin from 3.4.2 to 3.5.0org.apache.maven.plugins:maven-javadoc-plugin from 3.11.2 to 3.12.0org.apache.maven.plugins:maven-plugin-plugin from 3.15.1 to 3.15.2org.apache.maven.plugins:maven-release-plugin from 3.1.1 to 3.3.1org.apache.maven.plugins:maven-resources-plugin from 3.3.1 to 3.5.0org.apache.maven.plugins:maven-source-plugin from 3.3.1 to 3.4.0org.apache.maven.plugins:maven-surefire-plugin from 3.5.3 to 3.5.5org.codehaus.mojo:versions-maven-plugin from 2.18.0 to 2.21.0org.codehaus.mojo:exec-maven-plugin from 3.5.0 to 3.6.3org.jacoco:jacoco-maven-plugin from 0.8.13 to 0.8.14org.apache.maven.plugin-tools:maven-plugin-annotations from 3.15.1 to 3.15.2The 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>
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.
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 workaroundsIf 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 :-)
The main key-aspects that have been improved or being worked on are the following:
io.github.git-commit-id:git-commit-id-plugin-core from 6.0.0-rc.8 to 6.0.0
org.junit.jupiter:* from 5.10.2 to 5.12.2 (scope test)org.mockito:mockito-core from 5.12.0 to 5.18.0 (scope test)org.assertj:assertj-core from 3.26.0 to 3.27.3 (scope test)commons-io:commons-io from 2.16.1 to 2.19.0 (scope test)org.slf4j:slf4j-simple from 2.0.13 to 2.0.17 (scope test)org.apache.maven.plugins:maven-plugin-plugin from 3.13.1 to 3.15.1org.apache.maven.plugins:maven-dependency-plugin from 3.7.1 to 3.8.1org.apache.maven.plugins:maven-release-plugin from 3.1.0 to 3.1.1org.apache.maven.plugins:maven-compiler-plugin from 3.13.0 to 3.14.0org.apache.maven.plugins:maven-gpg-plugin from 3.2.4 to 3.2.7org.apache.maven.plugins:maven-clean-plugin from 3.4.0 to 3.4.1org.apache.maven.plugins:maven-jar-plugin from 3.4.1 to 3.4.2org.apache.maven.plugins:maven-surefire-plugin from 3.3.0 to 3.5.3org.apache.maven.plugins:maven-install-plugin from 3.1.2 to 3.1.4org.apache.maven.plugins:maven-deploy-plugin from 3.1.2 to 3.1.4org.apache.maven.plugins:maven-site-plugin from 3.12.1 to 3.21.0org.apache.maven.plugins:maven-javadoc-plugin from 3.7.0 to 3.11.2org.apache.maven.plugins:maven-release-plugin from 3.1.0 to 3.1.1The 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>
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.
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 workaroundsIf 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 :-)
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
org.apache.maven.plugins:maven-checkstyle-plugin from 3.3.1 to 3.4.0org.apache.maven.plugins:maven-release-plugin from 3.0.1 to 3.1.0org.apache.maven.plugins:maven-surefire-plugin from 3.2.5 to 3.3.0org.apache.maven.plugins:maven-clean-plugin from 3.3.2 to 3.4.0org.apache.maven.plugins:maven-dependency-plugin from 3.6.1 to 3.7.1The 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>
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.
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 workaroundsIf you find any problem with this plugin, feel free to report it here