git-commit-id/git-commit-id-maven-plugin (pl.project13.maven:git-commit-id-plugin)
### [`v4.9.10`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.9.10): Version 4.9.10 (The continued relocation saga)
[Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.9.9...v4.9.10)
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](https://togithub.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:
io.github.git-commit-idgit-commit-id-maven-plugin5.0.0
### [`v4.9.9`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.9.9): Version 4.9.9 (Relocation Release)
[Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.0.5...v4.9.9)
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](https://togithub.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
```xml
io.github.git-commit-idgit-commit-id-maven-plugin4.9.9
```
### [`v4.0.5`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.0.5): Version 4.0.5
[Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.0.4...v4.0.5)
Version 4.0.5 is finally there and includes various [bug-fixes and improvements](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues?q=milestone%3A4.0.5\&closed=1) :-)
#### New Features / Bug-Fixes:
The main key-aspects that have been improved or being worked on are the following:
- [#547](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/547) / [#540](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/540): add org.eclipse.jgit:org.eclipse.jgit.ssh.jsch as dependency
- [#548](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/548) / [#549](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/549): Plugin breaks if git config log.showSignature is 'true'
- [#556](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/556): update dependencies
#### Getting the latest release
The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), 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:
```xml
pl.project13.mavengit-commit-id-plugin4.0.5
```
#### 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 travis:
```xml
sonatype-snapshotsSonatype Snapshotshttps://oss.sonatype.org/content/repositories/snapshots/
```
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.
#### 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 [https://github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022)
- Using maven's plugin prefix resolution (e.g. `mvn com.test.plugins:myPlugin:myMojo`) might result in unresolved properties even with `true`. Please refer to [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287](https://togithub.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](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607) for details and potential workarounds
#### Reporting Problems
If you find any problem with this plugin, feel free to report it [here](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues)
### [`v4.0.4`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.0.4): Version 4.0.4
[Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.0.3...v4.0.4)
Version 4.0.4 is finally there and includes various [bug-fixes and improvements](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues?q=milestone%3A4.0.4\&closed=1) :-)
#### New Features / Bug-Fixes:
The main key-aspects that have been improved or being worked on are the following:
- [#531](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/531) / [#532](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/532): fix a `NullPointerException` when `session.getProjectDependencyGraph()` might be `null` when running the plugin from eclipse
- [#523](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/523) / [#534](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/534): Avoid illegal reflective access warning in JDK11
- [#539](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/539): Support Bitbucket Pipelines CI for build number and branch
- [#544](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/544): add support for author and commiter times (properties will be exposed as `git.commit.author.time`, `git.commit.committer.time`)
- [#529](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/529): update dependencies
#### Getting the latest release
The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), 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:
```xml
pl.project13.mavengit-commit-id-plugin4.0.4
```
#### 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 travis:
```xml
sonatype-snapshotsSonatype Snapshotshttps://oss.sonatype.org/content/repositories/snapshots/
```
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.
#### 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 [https://github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022)
- Using maven's plugin prefix resolution (e.g. `mvn com.test.plugins:myPlugin:myMojo`) might result in unresolved properties even with `true`. Please refer to [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287](https://togithub.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](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607) for details and potential workarounds
#### Reporting Problems
If you find any problem with this plugin, feel free to report it [here](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues)
### [`v4.0.3`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.0.3): Version 4.0.3
[Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.0.2...v4.0.3)
Version 4.0.3 is finally there and includes various [bug-fixes and improvements](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues?q=milestone%3A4.0.3\&closed=1) :-)
#### New Features / Bug-Fixes:
The main key-aspects that have been improved or being worked on are the following:
- [#525](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/525) / [#524](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/524): Update JGit dependency to 5.9.0.202009080501 (which fixes java.util.concurrent.RejectedExecutionException when using JGit concurrently in the same application -- see [here](https://bugs.eclipse.org/bugs/show_bug.cgi?id=564202) for further details)
- [#519](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/519) / [#520](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/520): made the plugin slightly smarter in terms of stripping the password from remote git urls that contain special characters. Note that this problem still can resurface when the url does not follow [rfc2396](https://www.ietf.org/rfc/rfc2396.txt). If processing fails the plugin will continue to print an error, but will avoid exposing the url in any generated properties (similar behaviour as before)
- [#501](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/501) / [#517](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/517): replace jackson-databind with lightweight javax.json to fix broken JSON format
- [#527](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/527): fix javadoc generation for java 12/13
#### Getting the latest release
The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), 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:
```xml
pl.project13.mavengit-commit-id-plugin4.0.3
```
#### 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 travis:
```xml
sonatype-snapshotsSonatype Snapshotshttps://oss.sonatype.org/content/repositories/snapshots/
```
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.
#### 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 [https://github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022)
- Using maven's plugin prefix resolution (e.g. `mvn com.test.plugins:myPlugin:myMojo`) might result in unresolved properties even with `true`. Please refer to [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287](https://togithub.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](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607) for details and potential workarounds
#### Reporting Problems
If you find any problem with this plugin, feel free to report it [here](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues)
### [`v4.0.2`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.0.2): Version 4.0.2
[Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.0.1...v4.0.2)
Version 4.0.2 is finally there and includes various [bug-fixes and improvements](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues?q=milestone%3A4.0.2\&closed=1) :-)
#### New Features / Bug-Fixes:
The main key-aspects that have been improved or being worked on are the following:
- [#469](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/469) / [#511](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/511) / [#512](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/512): Fix a condition where the plugin is not thread save when using `injectAllReactorProjects`
- [#509](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/509) / [#513](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/513): Allow initial `git.build.time` from `project.build.outputTimestamp` to support reproducible builds
- [#514](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/514): Update dependencies `jgit 5.8.1.202007141445-r`, `jackson-databind 2.11.2`, `joda-time 2.10.6`
#### Getting the latest release
The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), 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:
```xml
pl.project13.mavengit-commit-id-plugin4.0.2
```
#### 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 travis:
```xml
sonatype-snapshotsSonatype Snapshotshttps://oss.sonatype.org/content/repositories/snapshots/
```
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.
#### 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 [https://github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022)
- Using maven's plugin prefix resolution (e.g. `mvn com.test.plugins:myPlugin:myMojo`) might result in unresolved properties even with `true`. Please refer to [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287](https://togithub.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](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607) for details and potential workarounds
#### Reporting Problems
If you find any problem with this plugin, feel free to report it [here](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues)
### [`v4.0.1`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.0.1): Version 4.0.1
[Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.0.0...v4.0.1)
Version 4.0.1 is finally there and includes various [bug-fixes and improvements](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues?q=milestone%3A4.0.1\&closed=1) :-)
#### New Features / Bug-Fixes:
The main key-aspects that have been improved or being worked on are the following:
- [https://github.com/git-commit-id/git-commit-id-maven-plugin/pull/454](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/pull/454): add support for `git.branch` and `git.build.number` for GitHub Actions
- [https://github.com/git-commit-id/git-commit-id-maven-plugin/issues/457](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/457) / [https://github.com/git-commit-id/git-commit-id-maven-plugin/pull/460](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/pull/460): Add a `forceValueEvaluation`-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://github.com/git-commit-id/git-commit-id-maven-plugin/issues/459](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/459) / [https://github.com/git-commit-id/git-commit-id-maven-plugin/pull/460](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/pull/460): the git execution no longer fails on remote repository url's that don't follow a correct url-syntax (e.g. `https://:@git.server.com/pathToRepo.git`)
- [https://github.com/git-commit-id/git-commit-id-maven-plugin/issues/472](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/472) / [https://github.com/git-commit-id/git-commit-id-maven-plugin/pull/502](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/pull/502): prevent header timestamp in git.properties to allow for reproducible builds
- [https://github.com/git-commit-id/git-commit-id-maven-plugin/pull/493](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/pull/493): remove dependency on google guava
- [https://github.com/git-commit-id/git-commit-id-maven-plugin/pull/496](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/pull/496): add support for `git.branch` and `git.build.number` for AWS CodeBuild
- [https://github.com/git-commit-id/git-commit-id-maven-plugin/pull/503](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/pull/503): upgrade to jackson 2.11.1
#### Getting the latest release
The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), 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:
```xml
pl.project13.mavengit-commit-id-plugin4.0.1
```
#### 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 travis:
```xml
sonatype-snapshotsSonatype Snapshotshttps://oss.sonatype.org/content/repositories/snapshots/
```
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.
#### 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 [https://github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022)
- Using maven's plugin prefix resolution (e.g. `mvn com.test.plugins:myPlugin:myMojo`) might result in unresolved properties even with `true`. Please refer to [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287](https://togithub.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](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607) for details and potential workarounds
#### Reporting Problems
If you find any problem with this plugin, feel free to report it [here](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues)
### [`v4.0.0`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.0.0): Version 4.0.0
[Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v3.0.1...v4.0.0)
Version 4.0.0 is finally there and includes various [bug-fixes, improvements and some changes that can be considered as potential breaking changes](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues?q=milestone%3A4.0.0\&closed=1) :-)
The main key-aspects that have been improved or being worked on are the following:
#### Potential breaking changes:
- initial effort for modularisation (mainly splitting the project into a `maven` and a `core`-project) -- [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/441](https://togithub.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](https://togithub.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://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/387), [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/443](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/443)
#### New Features / Bug-Fixes:
- make `injectAllReactorProjects` slightly less verbose -- [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/431](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/431)
- allow to override `useNativeGit` from command line via `-Dmaven.gitcommitid.nativegit=true` -- [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/433](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/433)
- add support for `git.branch` and `git.build.number` for Azure DevOps -- [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/439](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/439)
- add support for `git.branch` and `git.build.number` for CircleCI -- [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/449](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/449)
- use maven's PluginParameterExpressionEvaluator to allow replacements with values that contain unresolved variables. E.g. allows to specify the `git.branch` in sonar's project version:
```xml
sonar.projectVersion^.*$${project.version}-${git.branch}false
```
See [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/444](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/444) for further details.
- update dependencies -- [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/437](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/437), [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/451](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/451)
- added tests for java 8, java 9, java 10, java 11, java 12 and java 13.
#### Getting the latest release
The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), 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:
```xml
pl.project13.mavengit-commit-id-plugin4.0.0
```
#### 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 travis:
```xml
sonatype-snapshotsSonatype Snapshotshttps://oss.sonatype.org/content/repositories/snapshots/
```
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.
#### 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 [https://github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022)
- Using maven's plugin prefix resolution (e.g. `mvn com.test.plugins:myPlugin:myMojo`) might result in unresolved properties even with `true`. Please refer to [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287](https://togithub.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](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607) for details and potential workarounds
- For some (undetermined) reason the plugin might fail with `org.eclipse.jgit.api.errors.TransportException: USERAUTH fail` under java 13 (I can't reproduce the issue), however a workaround would be specifying `true` or using the native git implementation with `true`.
#### Reporting Problems
If you find any problem with this plugin, feel free to report it [here](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues)
### [`v3.0.1`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v3.0.1): Version 3.0.1
[Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v3.0.0...v3.0.1)
Version 3.0.1 is finally there and includes various [bug-fixes and improvements](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues?q=milestone%3A3.0.1\&closed=1) :-)
#### New Features / Bug-Fixes:
The main key-aspects that have been improved or being worked on are the following:
- Added a new setting to control if the plugin should operate in offline mode -- [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/424](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/424) (by default the plugin will assume an 'online' mode and since version 3.0 will perform a `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).
- Removed the `org.apache.httpcomponents:httpclient` dependency -- [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/425](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/425)
- Since version 3.0.0 this plugin will now only ask for properties that are essential (proposal from [#185](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/185)). With this version the same technique is now also used when retrieving `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](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/428).
- Property caching now works properly for reactor builds using property caching when using `injectAllReactorProjects` -- [https://github.com/git-commit-id/maven-git-commit-id-plugin/pull/429](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/429).
#### Getting the latest release
The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), 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:
```xml
pl.project13.mavengit-commit-id-plugin3.0.1
```
#### 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 travis:
```xml
sonatype-snapshotsSonatype Snapshotshttps://oss.sonatype.org/content/repositories/snapshots/
```
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.
#### 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 [https://github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022)
- Using maven's plugin prefix resolution (e.g. `mvn com.test.plugins:myPlugin:myMojo`) might result in unresolved properties even with `true`. Please refer to [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287](https://togithub.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](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607) for details and potential workarounds
#### Reporting Problems
If you find any problem with this plugin, feel free to report it [here](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues)
### [`v3.0.0`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v3.0.0): Version 3.0.0
[Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v2.2.6...v3.0.0)
Version 3.0.0 is finally there and includes various [bug-fixes and improvements](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues?q=milestone%3A3.0.0\&closed=1) :-)
#### New Features / Bug-Fixes:
The main key-aspects that have been improved or being worked on are the following:
- **Java 1.7 is no longer supported** with this version and at least **Java 8 is required** - [#346](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/346)
- Introduced a more reliable way to deal with incremental builds for eclipse IDE - [#385](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/385) / [#366](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/366) / [#269](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/269)
- Added a new property for setting if branch name should be taken from build environment or not (e.g. set `false`). This behaviour might be useful in combination with the JGitflow maven plugin [#393](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/393).
- Moved the project to a new `git-commit-id` organization account [#384](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/384)
- Fixed a problem where the plugin hangs on windows under certain conditions and when there are too many changes in the git-repo [#396](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/396) / [#336](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/336)
- Allow the value of an replacementProperty to be empty [#400](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/400) / [#389](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/389)
- Introduced the new properties `git.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**. [#395](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/395)
- Instead of determine all properties and then exclude properties, this plugin will now only ask for properties that are essential (proposal from [#185](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/185)). For a detailed performance comparison refer to the [latest benchmark](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/408#issuecomment-487631736). **Note**: For users who want to avoid the the `git fetch` operation performed when gathering the properties `git.local.branch.ahead` and `git.local.branch.behind` simply exclude those to avoid that step:
```xml
^git.local.branch.*$
```
- Cleanup readme & Introduce coveralls [#380](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/380) / [#401](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/401) / [#405](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/405)
- The plugin tried to extract the Bamboo build variables with the wrong case [#410](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/410)
- Setting `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. [#403](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/403)
- Have travis finally automatically deploy the snapshot version of the plugin [#344](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/344) (see below how to get it)
- Setting `injectAllReactorProjects` 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](https://togithub.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](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/pull/414))
#### Getting the latest release
The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), 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:
```xml
pl.project13.mavengit-commit-id-plugin3.0.0
```
#### 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 travis:
```xml
sonatype-snapshotsSonatype Snapshotshttps://oss.sonatype.org/content/repositories/snapshots/
```
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.
#### 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 [https://github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022)
- Using maven's plugin prefix resolution (e.g. `mvn com.test.plugins:myPlugin:myMojo`) might result in unresolved properties even with `true`. Please refer to [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287](https://togithub.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](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607) for details and potential workarounds
#### Reporting Problems
If you find any problem with this plugin, feel free to report it [here](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
2.2.6->4.9.10Release Notes
git-commit-id/git-commit-id-maven-plugin (pl.project13.maven:git-commit-id-plugin)
### [`v4.9.10`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.9.10): Version 4.9.10 (The continued relocation saga) [Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.9.9...v4.9.10) 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](https://togithub.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:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.