Skip to content

Commit c1f4271

Browse files
committed
release-version: improve --skip-version-check docs
Document that it also skips the parent POM version check. And give a hint how to skip the check if you don't want it.
1 parent 2c49dc1 commit c1f4271

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

release-version.sh

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ Where <version> is the version to release. If omitted, it will prompt you.
9191
9292
Options include:
9393
--dry-run - Simulate the release without actually doing it.
94-
--skip-version-check - Violate SemVer version numbering intentionally.
94+
--skip-version-check - Skips the SemVer and parent pom version checks.
9595
--skip-license-update - Skips update of the copyright blurbs.
9696
--skip-push - Do not push to the remote git repository.
9797
--dev-version=<x.y.z> - Specify next development version explicitly;
@@ -154,7 +154,9 @@ test "$SKIP_VERSION_CHECK" -o "$parentGAV" != "${parentGAV#$}" || {
154154
latestParentVersion=$(sh -$- "$MAVEN_HELPER" latest-version "$parentGAV")
155155
currentParentVersion=${parentGAV##*:}
156156
test "$currentParentVersion" = "$latestParentVersion" ||
157-
die "Newer version of parent '${parentGAV%:*}' is available: $latestParentVersion"
157+
die "Newer version of parent '${parentGAV%:*}' is available: $latestParentVersion.
158+
I recommend you update it before releasing.
159+
Or if you know better, try again with --skip-version-check flag."
158160
}
159161

160162
# Check that the working copy is clean.

0 commit comments

Comments
 (0)