From cf64242e1f1e83573834136d504be3e3d52841ab Mon Sep 17 00:00:00 2001 From: Rob Winch Date: Thu, 11 Feb 2021 08:52:38 -0600 Subject: [PATCH] Updated Release Process (markdown) --- Release-Process.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Release-Process.md b/Release-Process.md index b2c52a7..a52ca94 100644 --- a/Release-Process.md +++ b/Release-Process.md @@ -40,12 +40,12 @@ Master is setup to use Gradle [dependency locking](https://docs.gradle.org/curre To lock the dependencies execute: ``` -./gradlew writeLocks --write-locks +./gradlew writeLocks --write-locks -PforceMavenRepositories=release ``` This writes out all the resolved versions. Run the build and if it passes, commit the changes. -**NOTE:** An issue may occur where a resolved version in a lock file includes a `BUILD-SNAPSHOT` version. For these scenarios, you can force to resolve the release version by appending the argument `-PforceMavenRepositories=release` to the above command. +**NOTE:** An issue may occur where a resolved version in a lock file includes a `BUILD-SNAPSHOT` version. To prevent that we force to resolve the release version by appending the argument `-PforceMavenRepositories=release` to the above command. ### 2. Update release version