Replace uppercase "SBT" with lowercase "sbt", and update some links to https BTW (#4706)

The lowercase spelling "sbt" seems to be the official spelling used in
their docs and other places. Shall we replace the uppercase "SBT"s with
this instead?

This is done for all occurences of "SBT" except for the link
http://www.lihaoyi.com/post/SowhatswrongwithSBT.html which will be
broken if updated.

Pull Request: #4706
---------

Co-authored-by: Tobias Roeser <[email protected]>

Author: ShreckYe

changelog.adoc

@@ -327,7 +327,7 @@ frameworks, etc.)
 6. The Mill doc-site at https://mill-build.org/ has undergone a massive overhaul.
 New comparisons with other build tools of (https://mill-build.org/mill/comparisons/maven.html[Maven],
 https://mill-build.org/mill/comparisons/gradle.html[Gradle],
-https://mill-build.org/mill/comparisons/sbt.html[SBT]), documentation for
+https://mill-build.org/mill/comparisons/sbt.html[`sbt`]), documentation for
 https://mill-build.org/mill/extending/new-language.html[adding new language toolchains]
 and https://mill-build.org/mill/extending/running-jvm-code.html[running dynamic JVM code],
 and re-organized the pages for Scala/Java/Kotlin by-use-case to make them more navigable

example/fundamentals/cross/10-static-blog/build.mill

@@ -138,4 +138,4 @@ def dist = Task {
 // This example use case is taken from the following blog post, which contains
 // some extensions and fun exercises to further familiarize yourself with Mill
 //
-// * http://www.lihaoyi.com/post/HowtocreateBuildPipelinesinScala.html[How to create Build Pipelines in Scala]
+// * https://www.lihaoyi.com/post/HowtocreateBuildPipelinesinScala.html[How to create Build Pipelines in Scala]

example/javalib/basic/4-compat-modules/build.mill

@@ -13,7 +13,7 @@ object foo extends MavenModule {
 }
 
 // `MavenModule` is a variant of `JavaModule`
-// that uses the more verbose folder layout of Maven, SBT, and other tools:
+// that uses the more verbose folder layout of Maven, `sbt`, and other tools:
 //
 // - `foo/src/main/java`
 // - `foo/src/test/java`

example/kotlinlib/basic/4-compat-modules/build.mill

@@ -20,7 +20,7 @@ object foo extends KotlinModule with KotlinMavenModule {
 }
 
 // `KotlinMavenModule` is a variant of `KotlinModule`
-// that uses the more verbose folder layout of Maven, SBT, and other tools:
+// that uses the more verbose folder layout of Maven, `sbt`, and other tools:
 //
 // - `foo/src/main/java`
 // - `foo/src/main/kotlin`

example/scalalib/basic/1-simple/build.mill

@@ -59,11 +59,11 @@ object foo extends ScalaModule {
 //         ...
 // ----
 //
-// NOTE: The default Mill source folder layout `foo/src/` differs from that of SBT's
+// NOTE: The default Mill source folder layout `foo/src/` differs from that of `sbt`'s
 // `foo/src/main/scala`.
-// If you wish to use the SBT source folder layout, e.g. for migrating
+// If you wish to use the `sbt` source folder layout, e.g. for migrating
 // an existing codebase, you should use
-// xref:#_sbt_compatible_modules[SBT-Compatible Modules]
+// xref:#_sbt_compatible_modules[`sbt`-Compatible Modules]
 //
 //// SNIPPET:END
 //

example/scalalib/basic/4-compat-modules/build.mill

@@ -1,9 +1,9 @@
 //// SNIPPET:ALL
 // Mill's default folder layout of `foo/src/` and `foo/test/src` differs from that
-// of SBT's `foo/src/main/scala/` and `foo/src/test/scala/`. If you are
-// migrating an existing codebase from SBT, you can use Mill's `SbtModule` and
+// of `sbt`'s `foo/src/main/scala/` and `foo/src/test/scala/`. If you are
+// migrating an existing codebase from `sbt`, you can use Mill's `SbtModule` and
 // `SbtTests` as shown below to preserve filesystem compatibility with an existing
-// SBT build:
+// `sbt` build:
 
 package build
 import mill._, scalalib._
@@ -25,7 +25,7 @@ trait BarModule extends CrossSbtModule {
 }
 
 // `SbtModule`/`CrossSbtModule` are variants of `ScalaModule`/`CrossScalaModule`
-// that use the more verbose folder layout of SBT, Maven, and other tools:
+// that use the more verbose folder layout of `sbt`, Maven, and other tools:
 //
 // - `foo/src/main/scala`
 // - `foo/src/main/scala-2.12`
@@ -39,8 +39,8 @@ trait BarModule extends CrossSbtModule {
 // - `foo/src-2.13`
 // - `foo/test/src`
 //
-// This is especially useful if you are migrating from SBT to Mill (or vice
-// versa), during which a particular module may be built using both SBT and
+// This is especially useful if you are migrating from `sbt` to Mill (or vice
+// versa), during which a particular module may be built using both `sbt` and
 // Mill at the same time
 
 /** Usage

example/scalalib/testing/2-test-deps/build.mill

@@ -4,7 +4,7 @@
 // --
 //
 // You might be used to test-scoped dependencies from other build tools like
-// Maven, Gradle or SBT. As test modules in Mill are just regular modules,
+// Maven, Gradle or `sbt`. As test modules in Mill are just regular modules,
 // there is no special need for a dedicated test-scope. You can use `ivyDeps`
 // and `runIvyDeps` to declare dependencies in test modules, and test modules
 // can use their `moduleDeps` to also depend on each other

integration/migrating/init/src/MillInitSbtTests.scala

@@ -10,7 +10,7 @@ import scala.collection.immutable.SortedSet
 object MillInitSbtUtils {
 
   /**
-   * bump sbt version to our tested version to resolve compatibility issues with lower sbt versions and higher JDK versions
+   * bump `sbt` version to our tested version to resolve compatibility issues with lower `sbt` versions and higher JDK versions
    */
   def bumpSbt(workspacePath: os.Path) =
     os.write.over(
@@ -27,7 +27,7 @@ object MillInitScala3ExampleProjectTests extends BuildGenTestSuite {
   def tests: Tests = Tests {
     /*
     - 17 KB
-    - sbt 1.10.7
+    - `sbt` 1.10.7
      */
     val url =
       "https://github.com/scala/scala3-example-project/archive/853808c50601e88edaa7272bcfb887b96be0e22a.zip"
@@ -51,7 +51,7 @@ object MillInitSbtScalaCsv200Tests extends BuildGenTestSuite {
   def tests: Tests = Tests {
     /*
     - 34 KB
-    - originally sbt 1.10.0
+    - originally `sbt` 1.10.0
      */
     val url = "https://github.com/tototoshi/scala-csv/archive/refs/tags/2.0.0.zip"
 
@@ -78,7 +78,7 @@ object MillInitSbtScalaCsv136Tests extends BuildGenTestSuite {
   def tests: Tests = Tests {
     /*
     - 28 KB
-    - originally sbt 1.2.8
+    - originally `sbt` 1.2.8
      */
     val url = "https://github.com/tototoshi/scala-csv/archive/refs/tags/1.3.6.zip"
 
@@ -106,7 +106,7 @@ object MillInitSbtMultiProjectExampleTests extends BuildGenTestSuite {
   def tests: Tests = Tests {
     /*
     - 12 KB
-    - originally sbt 1.0.2
+    - originally `sbt` 1.0.2
      */
     val url =
       "https://github.com/pbassiner/sbt-multi-project-example/archive/152b31df9837115b183576b0080628b43c505389.zip"
@@ -156,7 +156,7 @@ object MillInitSbtGatlingTests extends BuildGenTestSuite {
   def tests: Tests = Tests {
     /*
     - 1.8 MB
-    - sbt 1.10.7
+    - `sbt` 1.10.7
      */
     val url =
       "https://github.com/gatling/gatling/archive/711b8d4e7ac7aaa8d3173b2d77fb5e9c7843695a.zip"
@@ -250,13 +250,13 @@ object MillInitSbtGatlingTests extends BuildGenTestSuite {
               /*
               `java.util.MissingResourceException: Can't find bundle for base name gatling-version, locale ...`
               The version file in resources `gatling-commons/src/main/resources/gatling-version.properties`
-              is generated by a custom sbt task `generateVersionFileSettings`
+              is generated by a custom `sbt` task `generateVersionFileSettings`
               and therefore missing after conversion.
                */
               //
               "gatling-charts.test"
             ) ++ (if (Util.isWindows)
-                    // This fails on Windows with sbt too.
+                    // This fails on Windows with `sbt` too.
                     Seq("gatling-core.test")
                   else Seq.empty)
           ))

main/init/buildgen/src/mill/main/buildgen/BuildGenBase.scala

@@ -20,7 +20,7 @@ trait BuildGenBase[M, D, I] {
 
   /**
    * A [[Map]] mapping from a key retrieved from the original build tool
-   * (for example, the GAV coordinate for Maven, `ProjectRef.project` for sbt)
+   * (for example, the GAV coordinate for Maven, `ProjectRef.project` for `sbt`)
    * to the module FQN reference string in code such as `parentModule.childModule`.
    *
    * If there is no need for such a map, override it with [[Unit]].

main/init/buildgen/src/mill/main/buildgen/BuildGenUtil.scala

@@ -74,7 +74,7 @@ object BuildGenUtil {
         val declare =
           BuildGenUtil.renderTestModuleDecl(testModule, testModuleMainType, scopedDeps.testModule)
 
-        // `testSandboxWorkingDir` is disabled as other build tools such as sbt don't run tests in the sandbox.
+        // `testSandboxWorkingDir` is disabled as other build tools such as `sbt` don't run tests in the sandbox.
         s"""$declare {
            |
            |${renderBomIvyDeps(scopedDeps.testBomIvyDeps)}