chore(deps): update dependency pl.project13.maven:git-commit-id-plugin to v4.9.10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pl.project13.maven:git-commit-id-plugin (source)	4.0.4 -> 4.9.10

---

Release Notes

git-commit-id/git-commit-id-maven-plugin

v4.9.10

Compare Source

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 git-commit-id/git-commit-id-maven-plugin#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>

v4.9.9

Compare Source

This is a special release and should function in the same way as v4.0.5.

⚠️ WARNING
Based on the issue outlined in git-commit-id/git-commit-id-maven-plugin#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>

v4.0.5

Compare Source

Version 4.0.5 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

• #​547 / #​540: add org.eclipse.jgit:org.eclipse.jgit.ssh.jsch as dependency
• #​548 / #​549: Plugin breaks if git config log.showSignature is 'true'
• #​556: update dependencies

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>pl.project13.maven</groupId>
    <artifactId>git-commit-id-plugin</artifactId>
    <version>4.0.5</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by 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.

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 Heroku - .git directory is not found! Please specify a valid [dotGitDirectory] in your pom.xml git-commit-id/git-commit-id-maven-plugin#279 (comment)
• Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to Unable to obtaing git.branch property git-commit-id/git-commit-id-maven-plugin#287 or Unable to obtain git.branch property with SonarQube build git-commit-id/git-commit-id-maven-plugin#413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

---

Configuration

📅 Schedule: "before 3am on the first day of the month" in timezone Europe/Paris.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[codecov]

Codecov Report

Merging #78 (992c4d9) into master (85794e8) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              master       #78   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity        99        99           
===========================================
  Files              3         3           
  Lines            277       277           
  Branches          21        21           
===========================================
  Hits             277       277           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 85794e8...992c4d9. Read the comment docs.