Delany created MRELEASE-1140:
--------------------------------
Summary: New version suggestion should be based on previous release
Key: MRELEASE-1140
URL: https://issues.apache.org/jira/browse/MRELEASE-1140
Project: Maven Release Plugin
Issue Type: Improvement
Affects Versions: 3.0.1
Reporter: Delany
When i run *release:prepare* the plugin suggests what the new version should be.
On some of my projects it will suggest raising the minor version number, and on
others it suggests raising the patch version number.
Judging from experience, the algorithm looks at the FIRST release I made for
the project and will suggest that for eternity. So if for the first release I
bumped the minor version number, it will suggest changing that even if the last
10 times I bumped the patch number, e.g.
{code:java}
[INFO] 5/17 prepare:map-release-versions
What is the release version for "Thirdparty"? (thirdparty) 1.1.0: : 1.0.10
[INFO] 6/17 prepare:input-variables
What is the SCM release tag or label for "Thirdparty"? (thirdparty) v1.0.10: :
[INFO] 7/17 prepare:map-development-versions
What is the new development version for "Thirdparty"? (thirdparty)
1.1.0-SNAPSHOT: : 1.0.11-SNAPSHOT{code}
This is inconvenient. I would be better if it considered the LAST release only.
Perhaps there could be a configuration for this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
