search

aleksandr-m / gitflow-maven-plugin

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.
https://aleksandr-m.github.io/gitflow-maven-plugin/
Apache License 2.0
493 stars 181 forks source link

Semantic versioning for pom versions #208

Closed mjordan79 closed 2 years ago

mjordan79 commented 4 years ago

Hello, after reading the documentation, I still can't find a way for customizing generated POM versions with some prefixes while doing *-start operations. For example, assuming I want to start a release with gitflow:release-start, I would like to put the version 0.1.1-test in the POM instead of the default 0.0.1. Obviously, after a gitflow:release-finish I still want to maintain the default 0.0.1 version for the tag in the master branch, along with the same POM version.

Is this possible?

aleksandr-m commented 4 years ago

Feature name will be appended to version in feature goals by default. Is that what you are looking for?

mjordan79 commented 4 years ago

Feature name will be appended to version in feature goals by default. Is that what you are looking for?

Hello Aleksandr, thanks for the reply. Not for the feature branch, but for the release branch. Basically, I would like to obtain the same effect we have now for the feature branch. Assuming the release branch is configured with release/, I obtain the branch release/0.1.3 when doing a gitflow:release-start, but the maven version in the POM is 0.1.3. Would be possible to configure the plugin in order to change this version, for example 0.1.3-rc or 0.1.3-release, etc.?

aleksandr-m commented 4 years ago

What is your release flow looks like? You can set version with some qualifier on start goal and later update it manually or discard release branch and start a new one.