TheSnoozer

Hi @helterscelter thaks for reporting this here. This sounds like a great idea to go for. You got the point that it mostly needs some jgit-implementation adjustments... Ideas and PRs...

see: https://stackoverflow.com/questions/33038224/how-to-call-git-show-first-parent-in-jgit

Hi, thanks for reporting your issue here. This might be related to https://issues.apache.org/jira/browse/MNG-5725 and https://issues.apache.org/jira/browse/MNG-6434 if it is, which I suspect there is not much I can do (its a...

Thanks for the follow up! As mentioned I never tested this, but you are right my suggestion does not seem to work since `.*` is the greedy regex version. Using...

Hi, thanks for creating this ticket. I'm a bit surprised to see that there is apparently anything different between the v4.0.5 and v4.9.9 version. By looking at the [change-set](https://github.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.0.5...v4.9.9) I...

Holy cow, thanks for the investigation! I don't have any words for this. While I feel this is truly a correct bug, I can't change or delete already performed releases...

Indeed, I wanted to cut a 4.9.10 release to potentially fix this issue, but noticed that once I had the plugin installed locally I observed the **same issue** even when...

I have done the relocation as outlined in the relocation guide. It just breaks the plugin. The version 4.9.9 is the exact same version as 4.0.5. When I now would...

The only reason why there is a 4.9.9 release under the new coordinates is that it also broke maven (https://github.com/git-commit-id/git-commit-id-maven-plugin/issues/569). I don't want to publish a release under the old...

Despite my reluctance: There is now a [4.9.10](https://repo1.maven.org/maven2/pl/project13/maven/git-commit-id-plugin/4.9.10/) release under the old coordinates WITHOUT relocation information. At this point I just refuse to publish a 4.X under the new coordinates....