updated site

Author: eed3si9n

1.x/sitemap.xml

@@ -217,7 +217,7 @@ <h2 id="changing-buildsbt-dsl-to-scala-3x"><a class="header" href="#changing-bui
 </code></pre>
 <h2 id="bare-settings-changes"><a class="header" href="#bare-settings-changes">Bare settings changes</a></h2>
 <pre><code class="language-scala">version := "0.1.0"
-scalaVersion := "3.3.3"
+scalaVersion := "3.6.2"
 </code></pre>
 <p><em>Bare settings</em>, like the example above, are settings written directly in <code>build.sbt</code> without <code>settings(...)</code>.</p>
 <div id="admonition-warning" class="admonition admonish-warning" role="note" aria-labelledby="admonition-warning-title">
@@ -278,6 +278,19 @@ <h3 id="migrating--operator"><a class="header" href="#migrating--operator">Migra
 <pre><code class="language-scala">libraryDependencies += "org.scala-js" %% "scalajs-dom" % "2.8.0"
 </code></pre>
 <p>Use <code>.platform(Platform.jvm)</code> in case where JVM libraries are needed.</p>
+<h2 id="changes-to-target"><a class="header" href="#changes-to-target">Changes to <code>target</code></a></h2>
+<p>In sbt 2.x, the <code>target</code> directory is unified to be a single <code>target/</code> directory in the working directory, and each subproject creates a subdirectory encoding platform, Scala version, and the subproject id. To absorb this change in scripted tests, <code>exists</code>, <code>absent</code>, and <code>delete</code> now supports glob expression <code>**</code>, as well as <code>||</code>.</p>
+<pre><code class="language-bash"># before
+$ absent target/out/jvm/scala-3.3.1/clean-managed/src_managed/foo.txt
+$ exists target/out/jvm/scala-3.3.1/clean-managed/src_managed/bar.txt
+
+# after
+$ absent target/**/src_managed/foo.txt
+$ exists target/**/src_managed/bar.txt
+
+# either is ok
+$ exists target/**/proj/src_managed/bar.txt || proj/target/**/src_managed/bar.txt
+</code></pre>
 <h2 id="the-plugincompat-technique"><a class="header" href="#the-plugincompat-technique">The PluginCompat technique</a></h2>
 <p>To use the same <code>*.scala</code> source but target both sbt 1.x and 2.x, we can create a shim, for example an object named <code>PluginCompat</code> in both <code>src/main/scala-2.12/</code> and <code>src/main/scala-3/</code>.</p>
 <h3 id="migrating-classpath-type"><a class="header" href="#migrating-classpath-type">Migrating Classpath type</a></h3>

1.x/sitemap.xml.gz

@@ -225,13 +225,16 @@ <h1 id="sbt-20-changes-draft"><a class="header" href="#sbt-20-changes-draft">sbt
 <h2 id="changes-with-compatibility-implications"><a class="header" href="#changes-with-compatibility-implications">Changes with compatibility implications</a></h2>
 <p>See also <a href="./migrating-from-sbt-1.x.html">Migrating from sbt 1.x</a>.</p>
 <ul>
-<li>sbt 2.x uses Scala 3.x for build definitions and plugins (Both sbt 1.x and 2.x are capable of building Scala 2.x and 3.x) by <a href="https://github.com/eed3si9n">@eed3si9n</a>, <a href="https://github.com/adpi2">@adpi2</a>, and others.</li>
+<li>sbt 2.x uses Scala 3.x (currently <strong>3.6.2</strong>) for build definitions and plugins (Both sbt 1.x and 2.x are capable of building Scala 2.x and 3.x) by <a href="https://github.com/eed3si9n">@eed3si9n</a>, <a href="https://github.com/adpi2">@adpi2</a>, and others.</li>
 <li>Bare settings are added to all subprojects, as opposed to just the root subproject, and thus replacing the role that <code>ThisBuild</code> has played.</li>
 <li><code>test</code> task is changed to be incremental test that can cache test results. Use <code>testFull</code> for full test by <a href="https://github.com/eed3si9n">@eed3si9n</a> in <a href="https://github.com/sbt/sbt/pull/7686">#7686</a></li>
+<li>Default settings and tasks keys typed to <code>URL</code> <code>apiMappings</code>, <code>apiURL</code>, <code>homepage</code>, <code>organizationHomepage</code>, <code>releaseNotesURL</code> were changed to <code>URI</code> in <a href="https://github.com/sbt/sbt/pull/7927">#7927</a>.</li>
+<li><code>licenses</code> key is changed from <code>Seq[(String, URL)]</code> to <code>Seq[License]</code> in <a href="https://github.com/sbt/sbt/pull/7927">#7927</a>.</li>
 <li>sbt 2.x plugins are published with <code>_sbt2_3</code> suffix by <a href="https://github.com/eed3si9n">@eed3si9n</a> in <a href="https://github.com/sbt/sbt/pull/7671">#7671</a></li>
 <li>sbt 2.x adds <code>platform</code> setting so <code>ModuleID</code>'s <code>%%</code> operator can cross build on JVM as well as JS and Native, as opposed to <code>%%%</code> operator that was created in a plugin to workaround this issue, by <a href="https://github.com/eed3si9n">@eed3si9n</a> in <a href="https://github.com/sbt/sbt/pull/6746">#6746</a></li>
 <li>Dropped <code>useCoursier</code> setting so Coursier cannot be opted out, by <a href="https://github.com/eed3si9n">@eed3si9n</a> in <a href="https://github.com/sbt/sbt/pull/7712">#7712</a></li>
 <li><code>Key.Classpath</code> is changed to be an alias of the <code>Seq[Attributed[xsbti.HashedVirtualFileRef]]</code> type, instead of <code>Seq[Attributed[File]]</code>. Similarly, some task keys that used to return <code>File</code> have changed to return <code>HashedVirtualFileRef</code> instead. See <a href="../concepts/caching.html#caching-files">Caching Files</a>.</li>
+<li>In sbt 2.x <code>target</code> defaults to <code>target/out/jvm/scala-3.6.2/&lt;subproject&gt;/</code>, as opposed to <code>&lt;subproject&gt;/target/</code>.</li>
 </ul>
 <h3 id="dropped-dreprecations"><a class="header" href="#dropped-dreprecations">Dropped dreprecations</a></h3>
 <ul>
@@ -245,7 +248,7 @@ <h2 id="features"><a class="header" href="#features">Features</a></h2>
 </ul>
 <h3 id="common-settings"><a class="header" href="#common-settings">Common settings</a></h3>
 <p>In sbt 2.x, the bare settings in <code>build.sbt</code> are interpreted to be common settings, and are injected to all subprojects. This means we can now set <code>scalaVersion</code> without using <code>ThisBuild</code> scoping:</p>
-<pre><code class="language-scala">scalaVersion := "3.3.3"
+<pre><code class="language-scala">scalaVersion := "3.6.2"
 </code></pre>
 <p>This also fixes the so-called dynamic dispatch problem:</p>
 <pre><code class="language-scala">lazy val hi = taskKey[String]("")

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

@@ -230,14 +230,14 @@ <h2 id="historical-context"><a class="header" href="#historical-context">Histori
 <h2 id="project-matrix"><a class="header" href="#project-matrix">Project matrix</a></h2>
 <p>sbt 2.x introduces project matrix, which enables cross building to happen in parallel.</p>
 <pre><code class="language-scala">organization := "com.example"
-scalaVersion := "3.3.3"
+scalaVersion := "3.6.2"
 version      := "0.1.0-SNAPSHOT"
 
 lazy val core = (projectMatrix in file("core"))
   .settings(
     name := "core"
   )
-  .jvmPlatform(scalaVersions = Seq("3.3.3", "2.13.15"))
+  .jvmPlatform(scalaVersions = Seq("3.6.2", "2.13.15"))
 </code></pre>
 <p>See <a href="../reference/cross-building-setup.html">cross building setup</a> for more details on the setup.</p>
 

2.x/docs/en/changes/sbt-2.0-change-summary.html

@@ -268,7 +268,7 @@ <h3 id="vals-and-lazy-vals"><a class="header" href="#vals-and-lazy-vals"><code>v
 val toolkit = "org.scala-lang" %% "toolkit" % toolkitV
 val toolkitTest = "org.scala-lang" %% "toolkit-test" % toolkitV
 
-scalaVersion := "3.3.3"
+scalaVersion := "3.6.2"
 libraryDependencies += toolkit
 libraryDependencies += (toolkitTest % Test)
 </code></pre>

2.x/docs/en/concepts/cross-building.html

@@ -260,7 +260,7 @@ <h2 id="tracking-dependencies-in-one-place"><a class="header" href="#tracking-de
 To make it easier to use the <code>val</code>s defined in it, import <code>Dependencies.*</code> in your build.sbt file.</p>
 <pre><code class="language-scala">import Dependencies.*
 
-scalaVersion := "3.3.3"
+scalaVersion := "3.6.2"
 name := "something"
 libraryDependencies += toolkit
 libraryDependencies += toolkitTest % Test

2.x/docs/en/guide/build-definition-basics.html

@@ -216,7 +216,7 @@ <h1 id="multi-project-basics"><a class="header" href="#multi-project-basics">Mul
 other project.</p>
 <p>A project is defined by declaring a lazy val of type
 <a href="../../api/sbt/Project.html">Project</a>. For example, :</p>
-<pre><code class="language-scala">scalaVersion := "3.3.3"
+<pre><code class="language-scala">scalaVersion := "3.6.2"
 
 lazy val core = (project in file("core"))
   .settings(

2.x/docs/en/guide/library-dependency-basics.html

@@ -229,7 +229,7 @@ <h3 id="coursier"><a class="header" href="#coursier">Coursier</a></h3>
 <h3 id="zinc"><a class="header" href="#zinc">Zinc</a></h3>
 <p>Zinc is the incremental compiler for Scala, developed and maintained by sbt project.
 An often overlooked aspect of Zinc is that Zinc provides a stable API to invoke <strong>any modern versions</strong> of Scala compiler. Combined with the fact that Coursier can resolve any Scala version, with sbt we can invoke any modern versions of Scala just by writing a single line <code>build.sbt</code>:</p>
-<pre><code class="language-scala">scalaVersion := "3.3.3"
+<pre><code class="language-scala">scalaVersion := "3.6.2"
 </code></pre>
 <h3 id="bsp-server"><a class="header" href="#bsp-server">BSP server</a></h3>
 <p>sbt server supports <a href="https://build-server-protocol.github.io/">Build Server Protocol (BSP)</a> to list build targets, build them, etc.

2.x/docs/en/guide/multi-project-basics.html

@@ -219,7 +219,7 @@ <h1 id="the-book-of-sbt-draft"><a class="header" href="#the-book-of-sbt-draft">T
 integrates with IDEs like IntelliJ and VS Code,
 makes JAR packages, and publishes them to <a href="https://central.sonatype.com/">Maven Central</a>,
 JVM community's package registry.</p>
-<pre><code class="language-scala">scalaVersion := "3.3.3"
+<pre><code class="language-scala">scalaVersion := "3.6.2"
 </code></pre>
 <p>You just need one line of <code>build.sbt</code> to get started with Scala.</p>