updated site

Author: eed3si9n

1.x/sitemap.xml

@@ -12428,7 +12428,7 @@
     </url>
     <url>
         <loc>https://www.scala-sbt.org/1.x/docs/Combined+Pages.html</loc>
-        <lastmod>2025-10-04</lastmod>
+        <lastmod>2025-10-05</lastmod>
         <changefreq>daily</changefreq>
         <priority>0.9</priority>
     </url>
@@ -12584,7 +12584,7 @@
     </url>
     <url>
         <loc>https://www.scala-sbt.org/1.x/docs/offline/Combined+Pages.html</loc>
-        <lastmod>2025-10-04</lastmod>
+        <lastmod>2025-10-05</lastmod>
         <changefreq>daily</changefreq>
         <priority>0.9</priority>
     </url>
@@ -12692,7 +12692,7 @@
     </url>
     <url>
         <loc>https://www.scala-sbt.org/1.x/docs/offline/Community-Plugins.html</loc>
-        <lastmod>2025-10-04</lastmod>
+        <lastmod>2025-10-05</lastmod>
         <changefreq>daily</changefreq>
         <priority>0.9</priority>
     </url>
@@ -13424,7 +13424,7 @@
     </url>
     <url>
         <loc>https://www.scala-sbt.org/1.x/docs/Community-Plugins.html</loc>
-        <lastmod>2025-10-04</lastmod>
+        <lastmod>2025-10-05</lastmod>
         <changefreq>daily</changefreq>
         <priority>0.9</priority>
     </url>

1.x/sitemap.xml.gz

@@ -214,9 +214,10 @@ <h1 id="multi-project-basics"><a class="header" href="#multi-project-basics">Mul
 <p>Each subproject in a build has its own source directories, generates
 its own JAR file when you run <code>packageBin</code>, and in general works like any
 other project.</p>
-<p>A project is defined by declaring a lazy val of type
+<p>A <strong>subproject</strong> is defined by declaring a <code>lazy val</code> of type
 <a href="../../api/sbt/Project.html">Project</a>. For example, :</p>
 <pre><code class="language-scala">scalaVersion := "3.7.3"
+LocalRootProject / publish / skip := true
 
 lazy val core = (project in file("core"))
   .settings(
@@ -229,8 +230,69 @@ <h1 id="multi-project-basics"><a class="header" href="#multi-project-basics">Mul
     name := "util",
   )
 </code></pre>
-<p>The name of the val is used as the subproject's ID, which
-is used to refer to the subproject at the sbt shell.</p>
+<p>The name of the <code>val</code> is used as the subproject's ID, which
+is used to refer to the subproject in the sbt shell.</p>
+<p>sbt will always define a root project, so in the above build definition,
+we will have total of three subprojects.</p>
+<h2 id="subproject-dependency"><a class="header" href="#subproject-dependency">Subproject dependency</a></h2>
+<p>A subproject may depend on the code from another subproject.
+This is done by declaring <code>dependsOn(...)</code>. For example, if <code>util</code> needed <code>util</code> on its classpath, you would define <code>util</code> as:</p>
+<pre><code class="language-scala">lazy val util = (project in file("util"))
+  .dependsOn(core)
+</code></pre>
+<h2 id="task-aggregation"><a class="header" href="#task-aggregation">Task aggregation</a></h2>
+<p>Task aggregation means that running a task on the aggregate subproject will also run on the aggregated subprojects.</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val root = (project in file("."))
+  .autoAggregate
+  .settings(
+    publish / skip := true
+  )
+
+lazy val util = (project in file("util"))
+
+lazy val core = (project in file("core"))
+</code></pre>
+<p>In the above example, the root subproject aggregates <code>util</code> and <code>core</code>. When you type <code>compile</code> in the sbt shell, all tree subprojects are compiled in parallel.</p>
+<h2 id="root-project"><a class="header" href="#root-project">Root project</a></h2>
+<p>The subproject at the root of the build is called a <strong>root project</strong>,
+and often plays a special role in the build.
+If a subproject is not defined at the root directory of the build,
+sbt automatically creates a default one that aggregates all other subprojects in the build.</p>
+<h2 id="common-settings"><a class="header" href="#common-settings">Common settings</a></h2>
+<p>In sbt 2.x, bare settings that are written directly in <code>build.sbt</code> without <code>settings(...)</code> are <strong>common settings</strong> that are injected to all subprojects.</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val core = (project in file("core"))
+
+lazy val app = (project in file("app"))
+  .dependsOn(core)
+</code></pre>
+<p>In the above, the <code>scalaVersion</code> setting is applied to the default root subproject, <code>core</code>, and <code>util</code>.</p>
+<p>One exception to this rule is settings that are already scoped to a subproject.</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val core = (project in file("core"))
+
+lazy val app = (project in file("app"))
+  .dependsOn(core)
+
+// This is applied only to app
+app / name := "app1"
+</code></pre>
+<p>We can take advantage of this exception to add some settings that only apply to the default root project as follows:</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val core = (project in file("core"))
+
+lazy val app = (project in file("app"))
+  .dependsOn(core)
+
+// These are applied only to root
+LocalRootProject / name := "root"
+LocalRootProject / publish / skip := true
+</code></pre>
 
                     </main>
 

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

@@ -1285,9 +1285,10 @@ <h2 id="viewing-library-dependencies"><a class="header" href="#viewing-library-d
 <p>Each subproject in a build has its own source directories, generates
 its own JAR file when you run <code>packageBin</code>, and in general works like any
 other project.</p>
-<p>A project is defined by declaring a lazy val of type
+<p>A <strong>subproject</strong> is defined by declaring a <code>lazy val</code> of type
 <a href="guide/../../api/sbt/Project.html">Project</a>. For example, :</p>
 <pre><code class="language-scala">scalaVersion := "3.7.3"
+LocalRootProject / publish / skip := true
 
 lazy val core = (project in file("core"))
   .settings(
@@ -1300,8 +1301,69 @@ <h2 id="viewing-library-dependencies"><a class="header" href="#viewing-library-d
     name := "util",
   )
 </code></pre>
-<p>The name of the val is used as the subproject's ID, which
-is used to refer to the subproject at the sbt shell.</p>
+<p>The name of the <code>val</code> is used as the subproject's ID, which
+is used to refer to the subproject in the sbt shell.</p>
+<p>sbt will always define a root project, so in the above build definition,
+we will have total of three subprojects.</p>
+<h2 id="subproject-dependency"><a class="header" href="#subproject-dependency">Subproject dependency</a></h2>
+<p>A subproject may depend on the code from another subproject.
+This is done by declaring <code>dependsOn(...)</code>. For example, if <code>util</code> needed <code>util</code> on its classpath, you would define <code>util</code> as:</p>
+<pre><code class="language-scala">lazy val util = (project in file("util"))
+  .dependsOn(core)
+</code></pre>
+<h2 id="task-aggregation"><a class="header" href="#task-aggregation">Task aggregation</a></h2>
+<p>Task aggregation means that running a task on the aggregate subproject will also run on the aggregated subprojects.</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val root = (project in file("."))
+  .autoAggregate
+  .settings(
+    publish / skip := true
+  )
+
+lazy val util = (project in file("util"))
+
+lazy val core = (project in file("core"))
+</code></pre>
+<p>In the above example, the root subproject aggregates <code>util</code> and <code>core</code>. When you type <code>compile</code> in the sbt shell, all tree subprojects are compiled in parallel.</p>
+<h2 id="root-project"><a class="header" href="#root-project">Root project</a></h2>
+<p>The subproject at the root of the build is called a <strong>root project</strong>,
+and often plays a special role in the build.
+If a subproject is not defined at the root directory of the build,
+sbt automatically creates a default one that aggregates all other subprojects in the build.</p>
+<h2 id="common-settings"><a class="header" href="#common-settings">Common settings</a></h2>
+<p>In sbt 2.x, bare settings that are written directly in <code>build.sbt</code> without <code>settings(...)</code> are <strong>common settings</strong> that are injected to all subprojects.</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val core = (project in file("core"))
+
+lazy val app = (project in file("app"))
+  .dependsOn(core)
+</code></pre>
+<p>In the above, the <code>scalaVersion</code> setting is applied to the default root subproject, <code>core</code>, and <code>util</code>.</p>
+<p>One exception to this rule is settings that are already scoped to a subproject.</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val core = (project in file("core"))
+
+lazy val app = (project in file("app"))
+  .dependsOn(core)
+
+// This is applied only to app
+app / name := "app1"
+</code></pre>
+<p>We can take advantage of this exception to add some settings that only apply to the default root project as follows:</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val core = (project in file("core"))
+
+lazy val app = (project in file("app"))
+  .dependsOn(core)
+
+// These are applied only to root
+LocalRootProject / name := "root"
+LocalRootProject / publish / skip := true
+</code></pre>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="plugin-basics"><a class="header" href="#plugin-basics">Plugin basics</a></h1>
 <!--
 Please read the earlier pages in the Getting Started Guide first, in
@@ -1553,7 +1615,7 @@ <h2 id="features"><a class="header" href="#features">Features</a></h2>
 <li><strong>Local/remote cache system</strong>. Details below</li>
 <li><strong>Client-side run</strong>. Details below.</li>
 </ul>
-<h3 id="common-settings"><a class="header" href="#common-settings">Common settings</a></h3>
+<h3 id="common-settings-1"><a class="header" href="#common-settings-1">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.7.3"
 </code></pre>

2.x/docs/en/print.html

@@ -240,7 +240,7 @@ <h2 id="features"><a class="header" href="#features">Features</a></h2>
 <li><strong>Local/remote cache system</strong>. Details below</li>
 <li><strong>Client-side run</strong>. Details below.</li>
 </ul>
-<h3 id="common-settings"><a class="header" href="#common-settings">Common settings</a></h3>
+<h3 id="コモンセッティング"><a class="header" href="#コモンセッティング">コモン・セッティング</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.7.3"
 </code></pre>

2.x/docs/en/searchindex.js

@@ -3,7 +3,7 @@
     <head>
         <!-- Book generated using mdBook -->
         <meta charset="UTF-8">
-        <title>Multi project basics - The Book of sbt</title>
+        <title>マルチプロジェクトの基本 - The Book of sbt</title>
 
 
         <!-- Custom HTML head -->
@@ -208,11 +208,12 @@ <h1 class="menu-title">The Book of sbt</h1>
 
                 <div id="content" class="content">
                     <main>
-                        <h1 id="multi-project-basics"><a class="header" href="#multi-project-basics">Multi project basics</a></h1>
-<p>While a simple program can start out as a single-project build, it's more common for a build to split into smaller, multiple subprojects.</p>
-<p>Each subproject in a build has its own source directories, generates its own JAR file when you run <code>packageBin</code>, and in general works like any 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>
+                        <h1 id="マルチプロジェクトの基本"><a class="header" href="#マルチプロジェクトの基本">マルチプロジェクトの基本</a></h1>
+<p>簡単なプログラムならば単一プロジェクトから作り始めてもいいが、ビルドが複数の小さいのサブプロジェクトに分かれていくのが普通だ。</p>
+<p>ビルド内のサブプロジェクトは、それぞれ独自のソースディレクトリを持ち、<code>packageBin</code> を実行すると独自の JAR ファイルを生成するなど、概ね通常のプロジェクトと同様に動作する。</p>
+<p><strong>サブプロジェクト</strong>は、<code>lazy val</code> を用いて <a href="../../api/sbt/Project.html">Project</a> 型の値を宣言することで定義される。例えば:</p>
 <pre><code class="language-scala">scalaVersion := "3.7.3"
+LocalRootProject / publish / skip := true
 
 lazy val core = (project in file("core"))
   .settings(
@@ -225,7 +226,63 @@ <h1 id="multi-project-basics"><a class="header" href="#multi-project-basics">Mul
     name := "util",
   )
 </code></pre>
-<p>The name of the val is used as the subproject's ID, which is used to refer to the subproject at the sbt shell.</p>
+<p><code>val</code> 定義された変数名はプロジェクトの ID 及びベースディレクトリの名前になる。ID は sbt シェルからプロジェクトを指定する時に用いられる。</p>
+<p>sbt は必ずルートプロジェクトを定義するので、上の例のビルド定義は合計 3つのサブプロジェクトを持つ。</p>
+<h2 id="サブプロジェクト間依存性"><a class="header" href="#サブプロジェクト間依存性">サブプロジェクト間依存性</a></h2>
+<p>あるサブプロジェクトを、他のサブプロジェクトにあるコードに依存させたい場合、<code>dependsOn(...)</code> を使ってこれを宣言する。例えば、<code>util</code> に <code>core</code> のクラスパスが必要な場合は <code>util</code> の定義を次のように書く:</p>
+<pre><code class="language-scala">lazy val util = (project in file("util"))
+  .dependsOn(core)
+</code></pre>
+<h2 id="タスク集約"><a class="header" href="#タスク集約">タスク集約</a></h2>
+<p>タスク集約は、集約する側のサブプロジェクトで任意のタスクを実行するとき、集約される側の複数のサブプロジェクトでも同じタスクが実行されるという関係を意味する。</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val root = (project in file("."))
+  .autoAggregate
+  .settings(
+    publish / skip := true
+  )
+
+lazy val util = (project in file("util"))
+
+lazy val core = (project in file("core"))
+</code></pre>
+<p>上の例では、ルートプロジェクトが <code>util</code> と <code>core</code> を集約する。そのため、sbt シェルに <code>compile</code> と打ち込むと、3つのサブプロジェクトが並列にコンパイルされる。</p>
+<h2 id="ルートプロジェクト"><a class="header" href="#ルートプロジェクト">ルートプロジェクト</a></h2>
+<p>ビルドのルートにあるサブプロジェクトは、<strong>ルートプロジェクト</strong>と呼ばれ、ビルドの中で特別な役割を果たすことがある。もしルートディレクトリにサブプロジェクトが定義されてない場合、sbt は自動的に他のプロジェクトを集約するデフォルトのルートプロジェクトを生成する。</p>
+<h2 id="コモンセッティング"><a class="header" href="#コモンセッティング">コモン・セッティング</a></h2>
+<p>sbt 2.x系では、<code>settings(...)</code> を使わずに <code>build.sbt</code> にセッティングを直書きした場合、<strong>コモン・セッティング</strong>として全サブプロジェクトに注入される。</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val core = (project in file("core"))
+
+lazy val app = (project in file("app"))
+  .dependsOn(core)
+</code></pre>
+<p>上の例では、<code>scalaVersion</code> セッティングはデフォルトのルートプロジェクト、<code>core</code>、<code>util</code> に適用される。</p>
+<p>既にサブプロジェクトにスコープ付けされたセッティングはこのルールの例外となる。</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val core = (project in file("core"))
+
+lazy val app = (project in file("app"))
+  .dependsOn(core)
+
+// これは app のみに適用される
+app / name := "app1"
+</code></pre>
+<p>この例外を利用して、以下のように、ルートプロジェクトにのみ適用されるセッティングを書くことができる:</p>
+<pre><code class="language-scala">scalaVersion := "3.7.3"
+
+lazy val core = (project in file("core"))
+
+lazy val app = (project in file("app"))
+  .dependsOn(core)
+
+// これらは root にのみ適用される
+LocalRootProject / name := "root"
+LocalRootProject / publish / skip := true
+</code></pre>
 
                     </main>