The Git-Flow Maven Plugin supports various Git workflows, including GitFlow and GitHub Flow. This plugin runs Git and Maven commands from the command line.
I'm currently looking to migrate to this plugin. We're currently using the jGitFlow plugin. When using the following command:
mvn -B gitflow:hotfix-start -DuseSnapshotInRelease=true -DhotfixVersion=1.3.1 useSnapshotInHotfix=true -DpushRemote=true
The following will create a branch named hotfix-1.3.1 but with a pom version as <version>1.3.1</version>. For us, the version ideally would have "-SNAPSHOT" appended to the version. In order to get the version to have "-SNAPSHOT", the version would need to be specified as: hotfixVersion=1.3.1-SNAPSHOT. This has the side effect of the branch being named hotfix-1.31-SNAPSHOT. We would like the branch name to not have the -SNAPSHOT version in it. I was wondering if it would be possible to add an additional parameter that could control this behavior.
I suspect this happens also with release but have yet to try it.
I'm currently looking to migrate to this plugin. We're currently using the jGitFlow plugin. When using the following command:
mvn -B gitflow:hotfix-start -DuseSnapshotInRelease=true -DhotfixVersion=1.3.1 useSnapshotInHotfix=true -DpushRemote=true
The following will create a branch named hotfix-1.3.1 but with a pom version as
<version>1.3.1</version>
. For us, the version ideally would have "-SNAPSHOT" appended to the version. In order to get the version to have "-SNAPSHOT", the version would need to be specified as: hotfixVersion=1.3.1-SNAPSHOT. This has the side effect of the branch being named hotfix-1.31-SNAPSHOT. We would like the branch name to not have the -SNAPSHOT version in it. I was wondering if it would be possible to add an additional parameter that could control this behavior.I suspect this happens also with release but have yet to try it.