You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 1.x/docs/Basic-Def.html
+2-2
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@
44
44
<divclass="rightcolumn contents">
45
45
<h2id="Build+definition">Build definition<ahref="#Build+definition" class="header-link"><spanclass="header-link-content"> </span></a></h2><p>This page describes sbt build definitions, including some “theory” and
46
46
the syntax of <code>build.sbt</code>.
47
-
It assumes you have installed a recent version of sbt, such as sbt 1.9.7,
47
+
It assumes you have installed a recent version of sbt, such as sbt 1.9.8,
48
48
know how to <ahref="Running.html">use sbt</a>,
49
49
and have read the previous pages in the Getting Started Guide.
50
50
</p><p>This page discusses the <code>build.sbt</code> build definition.
This page describes sbt build definitions, including some "theory" and
1656
1656
the syntax of `build.sbt`.
1657
-
It assumes you have installed a recent version of sbt, such as sbt 1.9.7,
1657
+
It assumes you have installed a recent version of sbt, such as sbt 1.9.8,
1658
1658
know how to [use sbt][Running],
1659
1659
and have read the previous pages in the Getting Started Guide.
1660
1660
@@ -1669,7 +1669,7 @@ build the same projects with consistent results.
1669
1669
To do this, create a file named `project/build.properties` that specifies the sbt version as follows:
1670
1670
1671
1671
```
1672
-
sbt.version=1.9.7
1672
+
sbt.version=1.9.8
1673
1673
```
1674
1674
1675
1675
If the required version is not available locally,
@@ -4548,7 +4548,7 @@ always write it in all lowercase letters. However, we are cool with [酢豚][sub
4548
4548
4549
4549
#### My last command didn't work but I can't see an explanation. Why?
4550
4550
4551
-
sbt 1.9.7 by default suppresses most stack traces and debugging
4551
+
sbt 1.9.8 by default suppresses most stack traces and debugging
4552
4552
information. It has the nice side effect of giving you less noise on
4553
4553
screen, but as a newcomer it can leave you lost for explanation. To see
4554
4554
the previous output of a command at a higher verbosity, type
@@ -4921,7 +4921,7 @@ Any file name ending in `.sbt` will do, but most people use
4921
4921
4922
4922
### Miscellaneous
4923
4923
4924
-
#### Where can I find plugins for 1.9.7?
4924
+
#### Where can I find plugins for 1.9.8?
4925
4925
4926
4926
See [Community Plugins][Community-Plugins] for a list of currently available
4927
4927
plugins.
@@ -9319,7 +9319,7 @@ The following system properties can also be passed to `sbt`:
9319
9319
<tr>
9320
9320
<td><tt>sbt.version</tt></td>
9321
9321
<td>Version</td>
9322
-
<td><tt>1.9.7</tt></td>
9322
+
<td><tt>1.9.8</tt></td>
9323
9323
<td>sbt version to use, usually taken from <tt>project/build.properties</tt>.</td>
9324
9324
</tr>
9325
9325
@@ -12013,7 +12013,7 @@ sbt needs Scala jars to run itself since it is written in Scala. sbt
12013
12013
uses that same version of Scala to compile the build definitions that
12014
12014
you write for your project because they use sbt APIs. This version of
12015
12015
Scala is fixed for a specific sbt release and cannot be changed. For sbt
12016
-
1.9.7, this version is Scala 2.12.18. Because this Scala
12016
+
1.9.8, this version is Scala 2.12.18. Because this Scala
12017
12017
version is needed before sbt runs, the repositories used to retrieve
12018
12018
this version are configured in the sbt
12019
12019
[launcher][Sbt-Launcher].
@@ -17986,11 +17986,11 @@ This Parser definition will produce a value of type `(String,String)`.
17986
17986
The input syntax defined isn't very flexible; it is just a
17987
17987
demonstration. It will produce one of the following values for a
17988
17988
successful parse (assuming the current Scala version is 2.12.18,
17989
-
the current sbt version is 1.9.7, and there are 3 commands left to
17989
+
the current sbt version is 1.9.8, and there are 3 commands left to
17990
17990
run):
17991
17991
17992
17992
* (scala,2.12.18)
17993
-
* (sbt,1.9.7)
17993
+
* (sbt,1.9.8)
17994
17994
* (commands,3)
17995
17995
17996
17996
Again, we were able to access the current Scala and sbt version for the
@@ -20146,10 +20146,10 @@ If you haven't created one already, make sure to create `project/build.propertie
20146
20146
`sbt.version` number:
20147
20147
20148
20148
```yml
20149
-
sbt.version=1.9.7
20149
+
sbt.version=1.9.8
20150
20150
```
20151
20151
20152
-
Your build will now use 1.9.7.
20152
+
Your build will now use 1.9.8.
20153
20153
20154
20154
### Read the GitHub Actions manual
20155
20155
@@ -20449,10 +20449,10 @@ If you haven't created one already, make sure to create `project/build.propertie
20449
20449
`sbt.version` number:
20450
20450
20451
20451
```yml
20452
-
sbt.version=1.9.7
20452
+
sbt.version=1.9.8
20453
20453
```
20454
20454
20455
-
Your build will now use 1.9.7.
20455
+
Your build will now use 1.9.8.
20456
20456
20457
20457
### Read the Travis manual
20458
20458
@@ -20549,7 +20549,7 @@ java
20549
20549
-Xss6M
20550
20550
-XX:ReservedCodeCacheSize=256M
20551
20551
-jar
20552
-
/home/travis/.sbt/launchers/1.9.7/sbt-launch.jar
20552
+
/home/travis/.sbt/launchers/1.9.8/sbt-launch.jar
20553
20553
```
20554
20554
20555
20555
It seems to be working. One downside of setting all of the parameters is that we might be left behind when the environment updates and the default values gives us more memory in the future.
@@ -20575,7 +20575,7 @@ java
20575
20575
-XX:ReservedCodeCacheSize=256M
20576
20576
-Xms1024M
20577
20577
-jar
20578
-
/home/travis/.sbt/launchers/1.9.7/sbt-launch.jar
20578
+
/home/travis/.sbt/launchers/1.9.8/sbt-launch.jar
20579
20579
```
20580
20580
20581
20581
**Note**: This duplicates the `-Xms` flag as intended, which might not the best thing to do.
@@ -23513,7 +23513,7 @@ Here's how to set it up
23513
23513
#### project/build.properties
23514
23514
23515
23515
```
23516
-
sbt.version=1.9.7
23516
+
sbt.version=1.9.8
23517
23517
```
23518
23518
23519
23519
#### project/style.sbt
@@ -23564,7 +23564,7 @@ Let's try implementing a custom task called `compilecheck` that runs `Compile /
0 commit comments