From 889323e1f189339f17968ba54f64a61f6376a8bd Mon Sep 17 00:00:00 2001 From: William Narmontas Date: Sun, 21 Mar 2021 15:12:02 +0000 Subject: [PATCH] Inform the user how to find & verify the Coursier cache location Related to https://github.com/sbt/sbt/issues/5120 The `csr` key was not so obvious so should be mentioned in the docs. --- .../02-DetailTopics/01-Using-sbt/01-Command-Line-Reference.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/reference/02-DetailTopics/01-Using-sbt/01-Command-Line-Reference.md b/src/reference/02-DetailTopics/01-Using-sbt/01-Command-Line-Reference.md index 0edb4b275..6f76bd654 100644 --- a/src/reference/02-DetailTopics/01-Using-sbt/01-Command-Line-Reference.md +++ b/src/reference/02-DetailTopics/01-Using-sbt/01-Command-Line-Reference.md @@ -258,7 +258,7 @@ influence SBT execution. Also see [sbt launcher][Sbt-Launcher]. Directory CoursierDependencyResolution.defaultCacheLocation (in 1.3+) - Location of coursier artifact cache, where the default is defined by Coursier cache resolution logic. You should define sbt.coursier.home explicitly if you are using coursier in a CI environment and want to cache artifacts between runs. + Location of coursier artifact cache, where the default is defined by Coursier cache resolution logic. You can verify the value with the command `csrCacheDirectory`. You should define sbt.coursier.home explicitly if you are using coursier in a CI environment and want to cache artifacts between runs.