You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
release.useAutomaticVersion is nice for Jenkins/CI builds where the tagged version will be the version minus the -SNAPSHOT but when people want to cut major, minor, bug-fix releases (among other release types based on other versioning strategies), they need to specify the release.releaseVersion property to whatever version they want every time they cut a release.
It'd be nice if we could automate the setting of the releaseVersion property based on the release "type" that a user wants.
So along with using the release.useAutomaticVersion flag, we could make an optional second and/or complementary flag that looks something like:
Skip the prompt for confirming the release version
Change version to the correct next non-SNAPSHOT version for tag/release. ie if development version is 1.0.1-SNAPSHOT and I want to cut a major release, the tag would actually get bumped prior to release to 2.0.0. If I wanted a minor release, the tag would get bumped to 1.1.0.
The text was updated successfully, but these errors were encountered:
release.useAutomaticVersion
is nice for Jenkins/CI builds where the tagged version will be the version minus the-SNAPSHOT
but when people want to cut major, minor, bug-fix releases (among other release types based on other versioning strategies), they need to specify therelease.releaseVersion
property to whatever version they want every time they cut a release.It'd be nice if we could automate the setting of the
releaseVersion
property based on the release "type" that a user wants.So along with using the
release.useAutomaticVersion
flag, we could make an optional second and/or complementary flag that looks something like:This would:
1.0.1-SNAPSHOT
and I want to cut amajor
release, the tag would actually get bumped prior to release to2.0.0
. If I wanted aminor
release, the tag would get bumped to1.1.0
.The text was updated successfully, but these errors were encountered: