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... :-)
LGPL-3.0 License
Bot releases are hidden (Show)
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.0
org.apache.maven.plugins:maven-release-plugin
from 3.0.1
to 3.1.0
org.apache.maven.plugins:maven-surefire-plugin
from 3.2.5
to 3.3.0
org.apache.maven.plugins:maven-clean-plugin
from 3.3.2
to 3.4.0
org.apache.maven.plugins:maven-dependency-plugin
from 3.6.1
to 3.7.1
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>
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
Published by TheSnoozer 4 months ago
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 ⚠️
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:
Use javac --release
instead of -source
& -target
Delete BigDiffTest
bump several maven plugins
org.apache.maven.plugins:maven-assembly-plugin
from 3.7.0
to 3.7.1
org.apache.maven.plugins:maven-gpg-plugin
from 3.2.0
to 3.2.4
maven-plugin-plugin.version
from 3.11.0
to 3.12.0
org.apache.maven.plugins:maven-source-plugin
from 3.3.0
to 3.3.1
org.jacoco:jacoco-maven-plugin
from 0.8.11
to 0.8.12
org.apache.maven.plugins:maven-compiler-plugin
from 3.12.1
to 3.13.0
org.apache.maven.plugins:maven-jar-plugin
from 3.3.0
to 3.4.1
org.apache.maven.plugins:maven-install-plugin
from 3.1.1
to 3.1.2
org.apache.maven.plugins:maven-deploy-plugin
from 3.1.1
to 3.1.2
maven-plugin-plugin.version
from 3.12.0
to 3.13.0
org.codehaus.mojo:exec-maven-plugin
from 3.2.0
to 3.3.0
maven-plugin-plugin.version
from 3.13.0
to 3.13.1
org.apache.maven.plugins:maven-javadoc-plugin
from 3.6.3
to 3.7.0
org.apache.maven.plugins:maven-enforcer-plugin
from 3.4.1
to 3.5.0
bump several dependencies
2.15.1
to 2.16.1
2.0.12
to 2.0.13
(tests)5.11.0
to 5.12.0
(tests)3.25.3
to 3.26.0
(tests)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>
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
Published by TheSnoozer 7 months ago
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
Published by TheSnoozer 7 months ago
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
Published by TheSnoozer 8 months ago
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
Published by TheSnoozer 12 months ago
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
Published by TheSnoozer over 1 year ago
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
Published by TheSnoozer over 1 year ago
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
Published by TheSnoozer about 3 years ago
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>
Published by TheSnoozer over 3 years ago
This is a special release and should function in the same way as v4.0.5.
⚠️ 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>
Published by TheSnoozer over 3 years ago
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>
Now:
<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
Published by TheSnoozer over 3 years ago
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
Published by TheSnoozer over 3 years ago
Version 4.0.4 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:
NullPointerException
when session.getProjectDependencyGraph()
might be null
when running the plugin from eclipsegit.commit.author.time
, git.commit.committer.time
)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.4</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
Published by TheSnoozer almost 4 years ago
Version 4.0.3 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.3</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
Published by TheSnoozer about 4 years ago
Version 4.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:
injectAllReactorProjects
git.build.time
from project.build.outputTimestamp
to support reproducible buildsjgit 5.8.1.202007141445-r
, jackson-databind 2.11.2
, joda-time 2.10.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>pl.project13.maven</groupId>
<artifactId>git-commit-id-plugin</artifactId>
<version>4.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 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
Published by TheSnoozer over 4 years ago
Version 4.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:
git.branch
and git.build.number
for GitHub ActionsforceValueEvaluation
-switch to the replacementProperty
to tell the plugin that the value needs to be regenerated for every project. Note that this will make the plugin run for every project (e.g. which might be needed for sonar that requires unique keys for the sonar)https://:@git.server.com/pathToRepo.git
)git.branch
and git.build.number
for AWS CodeBuildThe 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.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 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
Published by TheSnoozer almost 5 years ago
Version 4.0.0 is finally there and includes various bug-fixes, improvements and some changes that can be considered as potential breaking changes :-)
The main key-aspects that have been improved or being worked on are the following:
maven
and a core
-project) -- https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/441 (initial idea https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/228)runOnlyOnce
coupled with Maven's --projects
parameter makes plugin not run at all -- https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/387, https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/443
injectAllReactorProjects
slightly less verbose -- https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/431
useNativeGit
from command line via -Dmaven.gitcommitid.nativegit=true
-- https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/433
git.branch
and git.build.number
for Azure DevOps -- https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/439
git.branch
and git.build.number
for CircleCI -- https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/449
git.branch
in sonar's project version:<replacementProperties>
<replacementProperty>
<property>sonar.projectVersion</property>
<token>^.*$</token>
<value>${project.version}-${git.branch}</value>
<regex>false</regex>
</replacementProperty>
</replacementProperties>
See https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/444 for further details.
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.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 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 workaroundsorg.eclipse.jgit.api.errors.TransportException: USERAUTH fail
under java 13 (I can't reproduce the issue), however a workaround would be specifying <offline>true</offline>
or using the native git implementation with <useNativeGit>true</useNativeGit>
.If you find any problem with this plugin, feel free to report it here
Published by TheSnoozer about 5 years ago
Version 3.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:
git fetch
operation to determine the properties git.local.branch.ahead
and git.local.branch.behind
. If the plugin is operating in 'offline' mode both those properties will only reflect the view of the local clone and thus might be off from the actual repository. Note this 'offline' mode is also respected when one set's the maven "-o" offline switch).org.apache.httpcomponents:httpclient
dependency -- https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/425
git.build.time
since the TimeZone.getTimeZone()
may also have an impact upon performance -- https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/428.injectAllReactorProjects
-- https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/429.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>3.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 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
Published by TheSnoozer over 5 years ago
Version 3.0.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:
<useBranchNameFromBuildEnvironment>false</useBranchNameFromBuildEnvironment>
). This behaviour might be useful in combination with the JGitflow maven plugin #393.git-commit-id
organization account #384git.local.branch.ahead
and git.local.branch.behind
that provide some information if the local branch is either ahead or behind the remote. Note that using this property will perform a git fetch
operation and may have a performance impact on the overall execution of the plugin. #395git fetch
operation performed when gathering the properties git.local.branch.ahead
and git.local.branch.behind
simply exclude those to avoid that step:<excludeProperties>
<excludeProperty>^git.local.branch.*$</excludeProperty>
</excludeProperties>
evaluateOnCommit
to anything besides the default HEAD
resulted only in the commit-id. in case users want to evaluateOnCommit
on any commit or branch that is not the default HEAD
, please be advised that this plugin will run git branch --points-at
that may or may not result in a git.branch
property that has multiple branches that are comma separated. If evaluateOnCommit
is kept as the default HEAD
the git.branch
property still may fallback to the commit-id. #403injectAllReactorProjects
to true for multi-modules project now stores the computed properties in the project context. If the properties are present in the project context this plugin will essentially reuse those properties from a previously computed version (kudus to https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/411, implemented in https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/414)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>3.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 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
Published by TheSnoozer almost 6 years ago
Version 2.2.6 is a security update for a potential issue within the jackson-databind dependency. As usual you can checkout the detailed list of bug-fixes :-)
The main key-aspects is a security update for a potential issue within the jackson-databind dependency. This specific dependency was updated to v2.9.8 in response to https://github.com/FasterXML/jackson-databind/issues/2186 (CVE-2018-19360, CVE-2018-19361, CVE-2018-19362). Even though by default an user of this plugin does not seem to be affected by this potential issue, it is highly recommended to adopt the latest version at your earliest convenience. Similar to version 2.2.5 this version provides full support for Java 7, Java 8, Java 9, Java 10 and Java 11 (and is potentially also working for any higher version).
The specific issues that have been fixed with the update of jackson-databind dependency are:
This plugin uses the jackson-databind dependency for dumping the git information (serialization) to the generated properties file and determining if the generated json properties are up-to-date (deserialization). As of now it appears that only user who generate json properties via <format>json</format>
may be affected by those issues. This specific configuration is set to <format>properties</format>
by default and hence by default it appears that those issues are out of scope. Only when this configuration is altered a user may need to consider the linked CVE's as potential security problem.
In general I would be unsure if this ever even could be considered a true attack vector of this plugin, since the generated json file would need to contain data that would trigger this specific bug in the dependency. If an adversary has access to the content to the location where the generated file is residing, I would assume he can also modify the any local file (including project files) and hence would not need to go through the pain and exploit this problem....
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>2.2.6</version>
</dependency>
If you find any problem with this plugin, feel free to report it here