EDIT

The jgitflow plugin version (M6) we are using seems not to be in the default maven repository. Last version there is M5.1 (https://mvnrepository.com/artifact/external.atlassian.jgitflow/jgit-flow-core/1.0-m5.1).

However, there are some other jgitflow plugins. The latest here: https://mvnrepository.com/artifact/ch.dvbern.oss.maven.jgitflow/jgitflow-maven-api/1.0-m8

We tried this out once but there is at least 1 problem to solve which is the handling of "versionNumberToIncrement" which was changed from int to Enum, resulting in an upgrade of Patch instead of Minor, as defined in our jenkins scripts: https://bitbucket.org/atlassian/jgit-flow/pull-requests/73/mjf-202-change-versionnumbertoincrement-to

Maybe it is possible to define the version number via plugin parameters in the pom.

We also need to check if we want to use jgitflow at all. According to AK not all projects use it anymore as it is not well developed/maintained and as it is easier if you can define exactly what you need yourself, not using a plugin.

links:

https://github.com/dvbern/jgitflow/tree/develop/jgitflow-maven-plugin/src
https://mvnrepository.com/artifact/com.atlassian.jgitflow/jgit-flow
https://bitbucket.org/atlassian/jgit-flow/src/master/pom.xml
https://bitbucket.org/atlassian/jgit-flow/src/develop/jgitflow-maven-plugin/src/main/java/com/atlassian/maven/plugins/jgitflow/mojo/BuildNumberMojo.java
https://groups.google.com/g/maven-jgitflow-users
https://bitbucket.org/atlassian/jgit-flow/wiki/Home
https://ultreiaio.gitlab.io/jgit-flow/jgitflow-maven-plugin/release-start-mojo.html