Allow development version to be specified via command-line #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To facilitate automation, we'd like to be able to specify the next development version as a maven property upon release-start. As of now, it is not possible in non-interactive mode to provide next development version, and the default strategy of incrementing the last digit may not be suitable for all teams.
example execution:
$ mvn gitflow:release-start -DdevelopmentVersion=1.2.0-SNAPSHOTThe documentation should be updated to include "developmentVersion" as an additional property for this goal.
Although these commits include changes to the of pom.xmls, please feel free to set these per your release process.
Thanks!