use sbt-dynver (#27042)

This commit is contained in:
Arnout Engelen 2019-12-16 14:33:17 +01:00 committed by GitHub
parent b5576870fc
commit 3a35851fef
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 19 additions and 11 deletions

View file

@ -251,7 +251,7 @@ declare -r current_version=$(get_current_version)
echolog "Current version is ${current_version}"
if [ "${current_version:0:3}" != "${version:0:3}" ]; then
fail "Releasing $version from wrong with version $current_version"
fail "Releasing $version from wrong branch with version $current_version"
fi
# start clean
@ -267,29 +267,29 @@ fi
# build the release
echolog "Building the release..."
if [ ! $dry_run ]; then
RELEASE_OPT="-Dakka.build.version=${version} -Dakka.genjavadoc.enabled=true -Dpublish.maven.central=true"
RELEASE_OPT="-Dakka.genjavadoc.enabled=true -Dpublish.maven.central=true"
else
RELEASE_OPT="-Dakka.build.version=${version} -Dakka.genjavadoc.enabled=true"
RELEASE_OPT="-Dakka.genjavadoc.enabled=true"
fi
try sbt $RELEASE_OPT +buildRelease
# tag this release
echolog "Tagging..."
try git tag -am "Version ${version}" v${version}
try sbt $RELEASE_OPT +buildRelease
try sbt $RELEASE_OPT buildDocs
echolog "Successfully created local release"
# check binary compatibility for dry run
if [ ! $no_mima ] && [ $dry_run ]; then
echodry "Running migration manager report..."
sbt $RELEASE_OPT +mimaReportBinaryIssues
try sbt $RELEASE_OPT +mimaReportBinaryIssues
echodry "Finished migration manager report"
fi
try sbt $RELEASE_OPT whitesourceCheckPolicies
# commit and tag this release
echolog "Tagging..."
try git tag -am "Version ${version}" v${version}
# the point of no return... we're now pushing out to servers
# use a special failure from now on