Page Comparison

...

This article describes the required steps to migrate from jgitflow-maven-plugin to gitflow-maven-plugin .

jgitflow-maven-plugin does not longer seem to be maintained, but is no longer maintained. The gitflow-maven-plugin is not a drop-in replacement and lacks some features (but has also additional features), but it’s very well maintained and provides a lot of additional features.

Adapt your project

If you have already used jgitflow-maven-plugin together with deriving your parent POM from wcm.io global-parent or aem-global-parent POM the migration is really easy.

...

The gitflow-maven-plugin provides no prompt during the release process for entering the new development version number that is used on the develop branch after the release. This means the new development version number is always calculated automatically.

The only possibility to You can influence this logic are with two optional parameters which you can pass with -D as system properties on the command line:

• versionDigitToIncrement parameter which controls which digit to increment in the next development version. Starts from zero. For example, if the release version is 1.2.3.4 and versionDigitToIncrement is set to 1 then the next development version will be 1.3.0.0-SNAPSHOT. If not set or set to not valid value defaults to increment last digit in the version.

• digitsOnlyDevVersion parameter which will remove qualifiers from the next development version if set to true. For example, if the release version is 1.0.0-Final then development version will be 1.0.1-SNAPSHOT. The default value is false (i.e. qualifiers will be preserved in next development version).

If this is not sufficient for you there these GitHub issue may help: #232, #235.you have more complex versioning schemes (e.g. even-odd versioning), you can configure a Maven Release Version Policy to be used. Example:

<plugin>
  <groupId>com.amashchenko.maven.plugin</groupId>
  <artifactId>gitflow-maven-plugin</artifactId>
  <configuration>
    <projectVersionPolicyId>OddEvenVersionPolicy</projectVersionPolicyId>
  </configuration>
  <dependencies>
    <dependency>
      <groupId>org.apache.maven.release</groupId>
      <artifactId>maven-release-oddeven-policy</artifactId>
      <version>3.0.0-M5</version>
    </dependency>
  </dependencies>
</plugin>

Details of the gitflow-maven-plugin configuration

...