Version 3.2.1 produces different version number than 3.2.0 for git

[apr4]

From version 3.2.1 this plugin uses the git command git log -1 --no-merges ...
Up to 3.2.0 the git command was git rev-parse --verify HEAD

This produces different results, if your workflow uses merges for release version. The version generated by the plugin does not match the actual SCM version.

[slawekjaranowski]

The change was did in apache/maven-scm#193

@kwin

[grumpymatt]

This seems like a pretty significant behavior change. Any way to get the previous behavior through config? We want the merge commit in our workflow.

[kwin]

Please open a bug over at https://issues.apache.org/jira/projects/SCM to request a flag to enable/disable skipMergeCommit behaviour (https://github.com/apache/maven-scm/pull/193/files#diff-54686f353f1a0410c924cc017f740c8b003de6770b46beddab45f48a30644a3dR66). However both JGit and Git CLI need to observe that flag. That should be a parameter similar to https://github.com/apache/maven-scm/blob/7f0b12ae405807ba42851681ca0899861af617af/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommand.java#L97.

There is already the API method https://maven.apache.org/scm/maven-scm-api/apidocs/src-html/org/apache/maven/scm/provider/ScmProvider.html#line.943 which allows for parametrization of the status call.