Bump io.github.git-commit-id:git-commit-id-maven-plugin from 9.1.0 to 10.0.0

[dependabot]

Bumps io.github.git-commit-id:git-commit-id-maven-plugin from 9.1.0 to 10.0.0.

Release notes

Sourced from io.github.git-commit-id:git-commit-id-maven-plugin's releases.

Version 10.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:

• #913 / #914: Require Maven 3.9.0 [Maven 3.6.3 is EOL] ⚠️

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>10.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 ktoso/maven-git-commit-id-plugin#279
• 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 git-commit-id/maven-git-commit-id-plugin#287 or git-commit-id/maven-git-commit-id-plugin#413 for details and potential workarounds

Reporting Problems

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

Full Changelog: git-commit-id/git-commit-id-maven-plugin@v9.2.0...v10.0.0

Version 9.2.0 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:

• bump several plugins
  • bump io.github.git-commit-id:git-commit-id-plugin-core from 6.1.5 to 6.2.0
    • replace org.eclipse.jgit.ssh.jsch with org.eclipse.jgit:org.eclipse.jgit.ssh.apache (see https://github.com/eclipse-jgit/jgit/blob/master/org.eclipse.jgit.ssh.jsch/README.md)

... (truncated)

Commits

• 2cd9c8b Bump version: 9.2.0 → 10.0.0
• fbfc066 Merge pull request #914 from git-commit-id/maven_3_9_0
• 3d51706 git-commit-id/git-commit-id-maven-plugin#913: Requi...
• fd9a262 update to the latest version available
• 0163ad6 Bump version: 9.1.0 → 9.2.0
• d8fdbb3 Merge pull request #912 from git-commit-id/plugin-core_6_2_0
• 8a33505 bump io.github.git-commit-id:git-commit-id-plugin-core from 6.1.5 to 6.2.0
• 4aefc60 update to the latest version in readme
• 743c415 update links to git-commit-id-maven-plugin (we are not in the core module :-)
• See full diff in compare view

[duncdrum]

These timeouts appear unrelated

[duncdrum]

@dependabot rebase

[line-o]

The breaking change is about the maven minimum version raised to

Require Maven 3.9.0

Is this true for the project as well? Do we enforce this. Because otherwise builds might break in unexpected ways for devs using older maven versions.

[duncdrum]

@line-o as far as I know using < 3.9.0 is already broken