chore(deps): update dependency io.github.git-commit-id:git-commit-id-maven-plugin to v7

This MR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.github.git-commit-id:git-commit-id-maven-plugin	6.0.0 -> 7.0.0

---

Release Notes

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

v7.0.0: Version 7.0.0

Compare Source

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 ⚠️

Potential Breaking changes:

The main key-aspects that might cause a breakage when migrating to the new version:

• Drop support for Maven 3.1.0-alpha-1 ⚠️
  • minimal required maven version is now Maven 3.2.5 (to support Maven 4.0.0)

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/issues/639 / https://github.com/git-commit-id/git-commit-id-maven-plugin/pull/642: Resolve worktree .git files to repository .git directory
• Update several plugins
  • updated git-commit-id-plugin-core from 6.0.0-rc.5 to 6.0.0-rc.6, that update brings
    • https://github.com/git-commit-id/git-commit-id-plugin-core/issues/57: Stop relying on javax.json 1.1.4
      • the dependency for javax.json:javax.json-api:1.1.4 was replaced with jakarta.json:jakarta.json-api:2.1.2
      • the dependency for org.glassfish:javax.json:1.1.4 was replaced with org.eclipse.parsson:parsson:1.1.4
    • bump jgit from 6.5.0.202303070854-r to 6.7.0.202309050840-r
    • bump commons-io:commons-io from 2.11.0 to 2.14.0
    • bump org.slf4j:slf4j-simple from 2.0.7 to 2.0.9
  • bump several maven plugins
    • bump maven-plugin-api from 3.1.0-alpha-1 to 3.9.2
    • bump maven-plugin-plugin from 3.6.0 to 3.9.0
    • bump maven-assembly-plugin from 3.4.2 to 3.6.0
    • bump maven-dependency-plugin from 3.5.0 to 3.6.0
    • bump maven-release-plugin from 3.0.0-M7 to 3.0.1
    • bump maven-enforcer-plugin from 3.2.1 to 3.4.1
    • bump maven-compiler-plugin from 3.8.1 to 3.11.0
    • bump maven-gpg-plugin from 3.1.0
    • bump maven-clean-plugin from 3.1.0 to 3.3.1
    • bump maven-resources-plugin from 3.1.0 to 3.3.1
    • bump maven-jar-plugin from 3.2.0 to 3.3.0
    • bump maven-surefire-plugin from 2.22.2 to 3.1.2
    • bump maven-install-plugin from 2.5.2 to 3.1.1
    • bump maven-javadoc-plugin from 3.2.0 to 3.6.0
    • bump maven-source-plugin from 3.2.1 to 3.3.0
  • Bump or replace various plugins for testing
    • bump commons-io:commons-io from 2.11.0 to 2.14.0 (test dependency)
    • bump org.slf4j:slf4j-simple from 2.0.7 to 2.0.9 (test dependency)
    • replace org.eluder.coveralls:coveralls-maven-plugin:4.3.0 with io.jsonwebtoken.coveralls:coveralls-maven-plugin:4.4.1 (test dependency)

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>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>7.0.0</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 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.

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
• 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 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 workarounds

Reporting Problems

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

---

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 MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

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

---

This MR has been generated by Renovate Bot.