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... :-)
Version 8.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:
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
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>
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 https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287 or https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607 for details and potential workaroundsIf 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 :-)
The main key-aspects that have been improved or being worked on are the following:
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>
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 https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287 or https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607 for details and potential workaroundsIf 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 ⚠️
The main key-aspects that might cause a breakage when migrating to the new version:
The main key-aspects that have been improved or being worked on are the following:
fatal: this operation must be run in a work tree
maven-plugin-plugin.version from 3.9.0 to 3.11.0
org.apache.maven.plugins:maven-dependency-plugin from 3.6.0 to 3.6.1
org.apache.maven.plugins:maven-surefire-plugin from 3.1.2 to 3.2.5
org.apache.maven.plugins:maven-checkstyle-plugin from 3.3.0 to 3.3.1
org.apache.maven.plugins:maven-clean-plugin from 3.3.1 to 3.3.2
org.apache.maven.plugins:maven-javadoc-plugin from 3.6.0 to 3.6.3
org.codehaus.mojo:exec-maven-plugin from 3.1.0 to 3.2.0
org.jacoco:jacoco-maven-plugin from 0.8.10 to 0.8.11
org.apache.maven.plugins:maven-compiler-plugin from 3.11.0 to 3.12.1
commons-io:commons-io from 2.14.0 to 2.15.1
org.mockito:mockito-core from 5.6.0 to 5.10.0
jakarta.xml.bind:jakarta.xml.bind-api from 2.3.3 to 4.0.1
org.slf4j:slf4j-simple from 2.0.9 to 2.0.12
org.assertj:assertj-core from 3.24.2 to 3.25.3
com.puppycrawl.tools:checkstyle from 8.25 to 10.13.0
actions/setup-java from 3 to 4
actions/cache from 3 to 4
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>
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 https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287 or https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607 for details and potential workaroundsIf 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 ⚠️
The main key-aspects that might cause a breakage when migrating to the new version:
The main key-aspects that have been improved or being worked on are the following:
javax.json:javax.json-api:1.1.4 was replaced with jakarta.json:jakarta.json-api:2.1.2
org.glassfish:javax.json:1.1.4 was replaced with org.eclipse.parsson:parsson:1.1.4
jgit from 6.5.0.202303070854-r to 6.7.0.202309050840-r
commons-io:commons-io from 2.11.0 to 2.14.0
org.slf4j:slf4j-simple from 2.0.7 to 2.0.9
maven-plugin-api from 3.1.0-alpha-1 to 3.9.2
maven-plugin-plugin from 3.6.0 to 3.9.0
maven-assembly-plugin from 3.4.2 to 3.6.0
maven-dependency-plugin from 3.5.0 to 3.6.0
maven-release-plugin from 3.0.0-M7 to 3.0.1
maven-enforcer-plugin from 3.2.1 to 3.4.1
maven-compiler-plugin from 3.8.1 to 3.11.0
maven-gpg-plugin from 3.1.0
maven-clean-plugin from 3.1.0 to 3.3.1
maven-resources-plugin from 3.1.0 to 3.3.1
maven-jar-plugin from 3.2.0 to 3.3.0
maven-surefire-plugin from 2.22.2 to 3.1.2
maven-install-plugin from 2.5.2 to 3.1.1
maven-javadoc-plugin from 3.2.0 to 3.6.0
maven-source-plugin from 3.2.1 to 3.3.0
commons-io:commons-io from 2.11.0 to 2.14.0 (test dependency)org.slf4j:slf4j-simple from 2.0.7 to 2.0.9 (test dependency)org.eluder.coveralls:coveralls-maven-plugin:4.3.0 with io.jsonwebtoken.coveralls:coveralls-maven-plugin:4.4.1 (test dependency)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>
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 https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287 or https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607 for details and potential workaroundsIf you find any problem with this plugin, feel free to report it here
Version 5.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:
org.apache.maven:maven-plugin-api and org.apache.maven:maven-core as <scope>provided</scope>
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>5.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 https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287 or https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607 for details and potential workaroundsIf you find any problem with this plugin, feel free to report it here
Version 6.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 main key-aspects that have been improved or being worked on are the following:
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>6.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 https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287 or https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607 for details and potential workaroundsIf you find any problem with this plugin, feel free to report it here
Where should I start....this release should not exists. Ideally the entire 4.9.9 "relocation" release was just intended to inform that the plugin moved to a new artifactId/groupId combination.
As outlined in https://github.com/git-commit-id/git-commit-id-maven-plugin/issues/571 or https://issues.apache.org/jira/browse/MNG-7204 there seems to be a problem where Maven will not forward the correct settings when you use the old coordinates with the 4.9.9 version. Since the 4.9.9 release contains relocation information it essentially became unusable triggering this "fix". Please note that the plugin is still moving to it's new coordinates. This 4.9.10 release is just a follow up to avoid any silent configuration issues being present somewhere....
TLDR: If you can use:
<groupId>io.github.git-commit-id</groupId>
<artifactId>git-commit-id-maven-plugin</artifactId>
<version>5.0.0</version>
This is a special release and should function in the same way as v4.0.5.
| :warning: WARNING |
|---|
| Based on the issue outlined in https://github.com/git-commit-id/git-commit-id-maven-plugin/issues/571 it is discouraged to use the old coordinates, since the plugin configuration might not be correctly applied to the plugin. Feel free to follow https://issues.apache.org/jira/browse/MNG-7204 for further informations. |
Initially this release was just intended to inform that the plugin moved to a new artifactId/groupId combination, but to avoid having published a release that might be considered broken I decided to just "fix" it. Currently the 4.9.9 release works only when using the new coordinates
<groupId>io.github.git-commit-id</groupId>
<artifactId>git-commit-id-maven-plugin</artifactId>
<version>4.9.9</version>
Version 5.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:
<groupId>pl.project13.maven</groupId>
<artifactId>git-commit-id-plugin</artifactId>
<groupId>io.github.git-commit-id</groupId>
<artifactId>git-commit-id-maven-plugin</artifactId>
The main key-aspects that have been improved or being worked on are the following:
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>5.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 https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287 or https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607 for details and potential workaroundsIf you find any problem with this plugin, feel free to report it here
Version 4.0.5 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:
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>pl.project13.maven</groupId>
<artifactId>git-commit-id-plugin</artifactId>
<version>4.0.5</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 travis:
<pluginRepositories>
<pluginRepository>
<id>sonatype-snapshots</id>
<name>Sonatype Snapshots</name>
<url>https://oss.sonatype.org/content/repositories/snapshots/</url>
</pluginRepository>
</pluginRepositories>
Even though travis 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 https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287 or https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607 for details and potential workaroundsIf you find any problem with this plugin, feel free to report it here