updated site

Author: eed3si9n

2.x/docs/en/changes/migrating-from-sbt-1.x.html

@@ -213,8 +213,26 @@ <h2 id="cross-building-sbt-plugins"><a class="header" href="#cross-building-sbt-
   )
   .jvmPlatform(scalaVersions = Seq("3.3.3", "2.12.20"))
 </code></pre>
-<p>If you use <code>projectMatrix</code>, make sure to move the plugin to a subdirectory like <code>plugin/</code>. Otherwise, the synthetic root project will also pick up the <code>src/</code>.
-Use sbt 1.10.2 or later to cross build from sbt 1.x side.</p>
+<p>If you use <code>projectMatrix</code>, make sure to move the plugin to a subdirectory like <code>plugin/</code>. Otherwise, the synthetic root project will also pick up the <code>src/</code>.</p>
+<h3 id="cross-building-sbt-plugin-with-sbt-1x"><a class="header" href="#cross-building-sbt-plugin-with-sbt-1x">Cross building sbt plugin with sbt 1.x</a></h3>
+<p>Use sbt 1.10.2 or later, if you want to cross build using sbt 1.x.</p>
+<pre><code class="language-scala">// using sbt 1.x
+lazy val scala212 = "2.12.20"
+lazy val scala3 = "3.3.4"
+ThisBuild / crossScalaVersions := Seq(scala212, scala3)
+
+lazy val plugin = (project in file("plugin"))
+  .enablePlugins(SbtPlugin)
+  .settings(
+    name := "sbt-vimquit",
+    (pluginCrossBuild / sbtVersion) := {
+      scalaBinaryVersion.value match {
+        case "2.12" =&gt; "1.5.8"
+        case _      =&gt; "2.0.0-M2"
+      }
+    },
+  )
+</code></pre>
 <h2 id="migrating-to-slash-syntax"><a class="header" href="#migrating-to-slash-syntax">Migrating to slash syntax</a></h2>
 <p>sbt 1.x supported both the sbt 0.13 style syntax and the slash syntax. sbt 2.x removes the support for the sbt 0.13 syntax, so use the slash syntax for both sbt shell and in <code>build.sbt</code>:</p>
 <pre><code class="language-scala">&lt;project-id&gt; / Config / intask / key

2.x/docs/en/guide/sbt-components.html

@@ -180,7 +180,7 @@ <h2 id="sbt-runner"><a class="header" href="#sbt-runner">sbt runner</a></h2>
 <p>An sbt build is executed using <code>sbt</code> runner, also called "sbt-the-shell-script" to distinguish from other components. It's important to note is that sbt runner is designed to run <strong>any version</strong> of sbt.</p>
 <h3 id="specifying-sbt-version-with-projectbuildproperties"><a class="header" href="#specifying-sbt-version-with-projectbuildproperties">Specifying sbt version with project/build.properties</a></h3>
 <p>sbt runner executes a subcomponent called sbt launcher, which reads <code>project/build.properties</code> to determine the sbt version for the build, and downloads the artifacts if they haven't been cached:</p>
-<pre><code>sbt.version=2.0.0-alpha7
+<pre><code>sbt.version=2.0.0-M2
 </code></pre>
 <p>This means that:</p>
 <ul>

2.x/docs/en/print.html

@@ -236,11 +236,11 @@ <h3 id="create-a-minimum-sbt-build"><a class="header" href="#create-a-minimum-sb
 cd foo-build
 touch build.sbt
 mkdir project
-echo "sbt.version=2.0.0-alpha7" &gt; project/build.properties
+echo "sbt.version=2.0.0-M2" &gt; project/build.properties
 </code></pre>
 <h3 id="start-sbt-shell"><a class="header" href="#start-sbt-shell">Start sbt shell</a></h3>
 <pre><code class="language-bash">$ sbt
-[info] welcome to sbt 2.0.0-alpha7 (Azul Systems, Inc. Java)
+[info] welcome to sbt 2.0.0-M2 (Azul Systems, Inc. Java)
 ....
 [info] started sbt server
 sbt:foo-build&gt;
@@ -868,7 +868,7 @@ <h2 id="sbt-runner"><a class="header" href="#sbt-runner">sbt runner</a></h2>
 <p>An sbt build is executed using <code>sbt</code> runner, also called "sbt-the-shell-script" to distinguish from other components. It's important to note is that sbt runner is designed to run <strong>any version</strong> of sbt.</p>
 <h3 id="specifying-sbt-version-with-projectbuildproperties"><a class="header" href="#specifying-sbt-version-with-projectbuildproperties">Specifying sbt version with project/build.properties</a></h3>
 <p>sbt runner executes a subcomponent called sbt launcher, which reads <code>project/build.properties</code> to determine the sbt version for the build, and downloads the artifacts if they haven't been cached:</p>
-<pre><code>sbt.version=2.0.0-alpha7
+<pre><code>sbt.version=2.0.0-M2
 </code></pre>
 <p>This means that:</p>
 <ul>
@@ -1478,8 +1478,26 @@ <h2 id="cross-building-sbt-plugins"><a class="header" href="#cross-building-sbt-
   )
   .jvmPlatform(scalaVersions = Seq("3.3.3", "2.12.20"))
 </code></pre>
-<p>If you use <code>projectMatrix</code>, make sure to move the plugin to a subdirectory like <code>plugin/</code>. Otherwise, the synthetic root project will also pick up the <code>src/</code>.
-Use sbt 1.10.2 or later to cross build from sbt 1.x side.</p>
+<p>If you use <code>projectMatrix</code>, make sure to move the plugin to a subdirectory like <code>plugin/</code>. Otherwise, the synthetic root project will also pick up the <code>src/</code>.</p>
+<h3 id="cross-building-sbt-plugin-with-sbt-1x"><a class="header" href="#cross-building-sbt-plugin-with-sbt-1x">Cross building sbt plugin with sbt 1.x</a></h3>
+<p>Use sbt 1.10.2 or later, if you want to cross build using sbt 1.x.</p>
+<pre><code class="language-scala">// using sbt 1.x
+lazy val scala212 = "2.12.20"
+lazy val scala3 = "3.3.4"
+ThisBuild / crossScalaVersions := Seq(scala212, scala3)
+
+lazy val plugin = (project in file("plugin"))
+  .enablePlugins(SbtPlugin)
+  .settings(
+    name := "sbt-vimquit",
+    (pluginCrossBuild / sbtVersion) := {
+      scalaBinaryVersion.value match {
+        case "2.12" =&gt; "1.5.8"
+        case _      =&gt; "2.0.0-M2"
+      }
+    },
+  )
+</code></pre>
 <h2 id="migrating-to-slash-syntax"><a class="header" href="#migrating-to-slash-syntax">Migrating to slash syntax</a></h2>
 <p>sbt 1.x supported both the sbt 0.13 style syntax and the slash syntax. sbt 2.x removes the support for the sbt 0.13 syntax, so use the slash syntax for both sbt shell and in <code>build.sbt</code>:</p>
 <pre><code class="language-scala">&lt;project-id&gt; / Config / intask / key
@@ -1606,7 +1624,7 @@ <h3 id="sbt-runner-and-sbt-server"><a class="header" href="#sbt-runner-and-sbt-s
 </ul>
 </li>
 </ul>
-<pre><code>sbt.version=2.0.0-alpha7
+<pre><code>sbt.version=2.0.0-M2
 </code></pre>
 <p>This mechanism allows builds to be configured to a specific version of sbt, and everyone working on the project would use the same build semantics, regardless of the sbt runner installed on their machine.</p>
 <p>This also means that some features are implemented at sbt runner or sbtn level, while other features are implemented at sbt server level.</p>
@@ -2349,7 +2367,7 @@ <h2 id="steps"><a class="header" href="#steps">Steps</a></h2>
 <ol>
 <li>Create a fresh directory, like <code>hello_scala/</code></li>
 <li>Create a directory named <code>project/</code> under <code>hello_scala/</code>, and create <code>project/build.properties</code> with
-<pre><code>sbt.version=2.0.0-alpha7
+<pre><code>sbt.version=2.0.0-M2
 </code></pre>
 </li>
 <li>Under <code>hello_scala/</code>, create <code>build.sbt</code>:

2.x/docs/en/recipes/hello-world.html

@@ -182,7 +182,7 @@ <h2 id="steps"><a class="header" href="#steps">Steps</a></h2>
 <ol>
 <li>Create a fresh directory, like <code>hello_scala/</code></li>
 <li>Create a directory named <code>project/</code> under <code>hello_scala/</code>, and create <code>project/build.properties</code> with
-<pre><code>sbt.version=2.0.0-alpha7
+<pre><code>sbt.version=2.0.0-M2
 </code></pre>
 </li>
 <li>Under <code>hello_scala/</code>, create <code>build.sbt</code>:

2.x/docs/en/reference/sbt.html

@@ -198,7 +198,7 @@ <h3 id="sbt-runner-and-sbt-server"><a class="header" href="#sbt-runner-and-sbt-s
 </ul>
 </li>
 </ul>
-<pre><code>sbt.version=2.0.0-alpha7
+<pre><code>sbt.version=2.0.0-M2
 </code></pre>
 <p>This mechanism allows builds to be configured to a specific version of sbt, and everyone working on the project would use the same build semantics, regardless of the sbt runner installed on their machine.</p>
 <p>This also means that some features are implemented at sbt runner or sbtn level, while other features are implemented at sbt server level.</p>

2.x/docs/en/sbt-by-example.html

@@ -183,11 +183,11 @@ <h3 id="create-a-minimum-sbt-build"><a class="header" href="#create-a-minimum-sb
 cd foo-build
 touch build.sbt
 mkdir project
-echo "sbt.version=2.0.0-alpha7" &gt; project/build.properties
+echo "sbt.version=2.0.0-M2" &gt; project/build.properties
 </code></pre>
 <h3 id="start-sbt-shell"><a class="header" href="#start-sbt-shell">Start sbt shell</a></h3>
 <pre><code class="language-bash">$ sbt
-[info] welcome to sbt 2.0.0-alpha7 (Azul Systems, Inc. Java)
+[info] welcome to sbt 2.0.0-M2 (Azul Systems, Inc. Java)
 ....
 [info] started sbt server
 sbt:foo-build&gt;