subutai

Experiments with SBT.

Simplest SBT project setup (with new github repo)

Create repository (like subutai)
In it touch build.sbt
Set scala version(s) in build.sbt Add this line to build.sbt:
ThisBuild / scalaVersion := "2.13.2"
Create project/build.properties with the following content:
sbt.version = 1.3.12.
Use sbt> reboot if changed.
If needed, add .gitignore and LICENSE

Now you can clone this new repository on your desktop with
git clone https://github.com/whitechno/subutai.git,
and open and edit it with your favorite IDE.

Now you have a minimal setup to start using Scala with SBT.

You can also switch scalaVersion temporarily:
sbt:Hello> ++2.12.11! -v
! is to force version switch (without it, the switch happens only in projects where this particular version is included in crossScalaVersions of project settings)
-v is for verbose

Versions of key dependencies

SBT
https://github.com/sbt/sbt/releases
- 1.10.0 - May 05, 2024
- 1.9.9 - Feb 22, 2024
  - To fix sbt 1.9.8's UnsatisfiedLinkError with stat, sbt 1.9.9 removes native code that was used to get the millisecond-precision timestamp that was broken (JDK-8177809) on JDK 8 prior to OpenJDK 8u302.
- 1.9.8 - Dec 13, 2023
- 1.9.7 - Oct 22, 2023
- 1.9.6 - Sep 15, 2023
- 1.9.5 - Sep 13, 2023 - broken, don't use it
- 1.9.4 - Aug 23, 2023
- 1.9.3 - Jul 23, 2023
- 1.9.2 - Jul 09, 2023
- 1.9.1 - Jun 25, 2023
- 1.9.0 - Jun 02, 2023
- 1.8.3 - May 12, 2023
- 1.8.2 - Jan 04, 2023
- 1.8.1 - Jan 03, 2023
- 1.8.0 - Nov 10, 2022
- 1.7.3 - Oct 30, 2022
- 1.7.2 - Oct 02, 2022
- 1.7.1 - Jul 11, 2022
- 1.7.0 - Jul 10, 2022
- 1.6.2 - Jan 31, 2022
- 1.6.1 - Dec 28, 2021
- 1.6.0 - Dec 26, 2021
- 1.5.8 - Dec 20, 2021
- 1.5.7 - Dec 14, 2021
- 1.5.6 - Dec 09, 2021
- 1.5.5 - Jul 12, 2021
- 1.5.4 - Jun 13, 2021
- 1.5.3 - May 31, 2021
- 1.5.2 - May 09, 2021
- 1.5.1 - Apr 25, 2021
- 1.5.0 - Apr 04, 2021
- 1.4.9 - Mar 09, 2021
- 1.4.8 - Mar 07, 2021
- 1.4.7 - Jan 30, 2021
- 1.4.6 - Dec 24, 2020
- 1.4.5 - Dec 13, 2020
- 1.4.4 - Nov 22, 2020
- 1.4.3 - Nov 15, 2020
- 1.4.2 - Nov 01, 2020
- 1.4.1 - Oct 19, 2020
- 1.4.0 - Oct 04, 2020
- 1.3.13 - Jun 27, 2020
- 1.3.12 - May 30, 2020
- 1.3.11 - May 29, 2020
  - There was a regression in sbt 1.3.11. Please use sbt 1.3.12 instead.
- 1.3.10 - Apr 14, 2020
- 1.3.9 - Mar 31, 2020
- 1.3.8 - Feb 3, 2020
Scala
https://github.com/scala/scala/releases
- 2.13
  - 2.13.14 - May 01, 2024
  - 2.13.13 - Feb 26, 2024
    - Support binary integer literals using 0b, as in Java. For example:
      scala> 0b00101010 val res0: Int = 42
  - 2.13.12 - Sep 11, 2023
  - 2.13.11 - Jun 07, 2023
  - 2.13.10 - Oct 13, 2022
  - 2.13.9 - Sep 21, 2022
    - Library maintainers should avoid publishing libraries using Scala 2.13.9. Please use 2.13.10 instead. 2.13.9 has a regression where binary-incompatible bytecode is emitted for case classes which are also value classes (case class ... extends AnyVal).
  - 2.13.8 - Jan 12, 2022
  - 2.13.7 - Nov 01, 2021
  - 2.13.6 - May 17, 2021
  - 2.13.5 - Feb 22, 2021
  - 2.13.4 - Nov 19, 2020
  - 2.13.3 - Jun 25, 2020
  - 2.13.2 - Apr 22, 2020
  - 2.13.1 - Sep 18, 2019
- 2.12
  - 2.12.19 - Feb 26, 2024
  - 2.12.18 - Jun 07, 2023
  - 2.12.17 - Sep 16, 2022
  - 2.12.16 - Jun 10, 2022
  - 2.12.15 - Sep 14, 2021
  - 2.12.14 - May 27, 2021
  - 2.12.13 - Jan 12, 2021
  - 2.12.12 - Jul 12, 2020
  - 2.12.11 - Mar 16, 2020
  - 2.12.10 - Sep 10, 2019
- 2.11 & 2.10
  - 2.11.12 - Nov 9, 2017
  - 2.10.7 - Nov 9, 2017
ScalaTest
https://www.scalatest.org
https://github.com/scalatest/scalatest/releases
- 3.2.18 - Feb 7, 2024
- 3.2.17 - Sep 12, 2023
- 3.2.16 - May 15, 2023
- 3.2.15 - Jan 06, 2023
- 3.2.14 - Sep 29, 2022
- 3.2.13 - Jul 30, 2022
- 3.2.12 - May 05, 2022
- 3.2.11 - Jan 25, 2022
- 3.2.10 - Sep 20, 2021
- 3.2.9 - May 17, 2021
- 3.2.8 - Apr 21, 2021
- 3.2.7 - Apr 02, 2021
- 3.2.6 - Mar 08, 2021
- 3.2.5 - Feb 23, 2021
- 3.2.4 - Feb 18, 2021
- 3.2.3 - Nov 09, 2020
- 3.2.2 - Sep 04, 2020
- 3.2.1 - Aug 11, 2020
- 3.2.0 - Jun 20, 2020
- 3.1.4 - Sep 04, 2020
- 3.1.2 - May 13, 2020
- 3.1.1 - Feb 20, 2020
- 3.1.0 - Nov 28, 2019
ScalaCheck
https://github.com/typelevel/scalacheck/releases
- 1.18.0 - Apr 17, 2024
- 1.17.1 - Apr 16, 2024
- 1.17.0 - Sep 15, 2022
- 1.16.0 - Apr 07, 2022
- 1.15.4 - May 03, 2021
- 1.15.3 - Mar 29, 2021 (drops Scala 2.11 on Jan 22, 2021)
- 1.15.2 - Dec 20, 2020 Last version still available for Scala 2.11
- 1.15.1 - Nov 06, 2020
- 1.15.0 - Oct 31, 2020
- 1.14.3 - Dec 14, 2019 Last version still available for Scala 2.10
- 1.14.2 - Sep 25, 2019
- 1.14.1 - Sep 17, 2019
- 1.14.0 - Apr 22, 2018
typesafe config https://github.com/lightbend/config/tags
- 1.4.3 - Oct 17, 2023
- 1.4.2 - Feb 01, 2022
- 1.4.1 - Oct 22, 2020
- 1.4.0 - Oct 14, 2019
- 1.3.4 - Apr 18, 2019
- 1.3.0 - May 8, 2015
- 1.2.1 - May 2, 2014
- 1.2.0 - Jan 15, 2014
sbt-scalafmt (Scalafmt sbt plugin)
https://github.com/scalameta/sbt-scalafmt/releases
- 2.5.2 - Aug 30, 2023
- 2.5.1 - Aug 29, 2023
- 2.5.0 - Nov 14, 2022
- 2.4.6 - Dec 24, 2021
- 2.4.5 - Dec 04, 2021
- 2.4.4 - Nov 18, 2021
- 2.4.3 - Jul 08, 2021
- 2.4.2 - Aug 01, 2020
- 2.4.0 - May 14, 2020
- 2.3.4 - Apr 10, 2020
- 2.3.3 - Apr 10, 2020
- 2.3.2 - Mar 5, 2020
- 2.3.1 - Jan 27, 2020
- 2.3.0 - Dec 9, 2019
Scalafmt
https://github.com/scalameta/scalafmt/releases
- 3.8.1 - Mar 29, 2024
- 3.8.0 - Feb 19, 2024
- 3.7.17 - Nov 16, 2023
- 3.7.16 - Nov 10, 2023
- 3.7.15 - Oct 24, 2023
- 3.7.14 - Sep 01, 2023
- 3.7.13 - Aug 28, 2023
- 3.7.12 - Aug 03, 2023
- 3.7.11 - Jul 26, 2023
- 3.7.10 - Jul 16, 2023
- 3.7.9 - Jul 12, 2023
- 3.7.8 - Jul 10, 2023
- 3.7.7 - Jul 05, 2023
- 3.7.6 - Jul 03, 2023
- 3.7.5 - Jun 29, 2023
- 3.7.4 - May 30, 2023
- 3.7.3 - Mar 28, 2023
- 3.7.2 - Feb 23, 2023
- 3.7.1 - Jan 23, 2023
- 3.7.0 - Jan 18, 2023
- 3.6.1 - Oct 31, 2022
- 3.6.0 - Oct 17, 2022
- 3.5.9 - Aug 11, 2022
- 3.5.8 - Jun 01, 2022
- 3.5.7 - May 25, 2022
- 3.5.5 - May 24, 2022
- 3.5.4 - May 18, 2022
- 3.5.3 - May 13, 2022
- 3.5.2 - Apr 18, 2022
- 3.5.1 - Apr 06, 2022
- 3.5.0 - Apr 01, 2022
- 3.4.3 - Feb 11, 2022
- 3.4.2 - Feb 05, 2022
- 3.4.1 - Feb 05, 2022
- 3.4.0 - Jan 28, 2022
- 3.3.3 - Jan 22, 2022
- 3.3.2 - Jan 19, 2022
- 3.3.1 - Jan 01, 2022
- 3.3.0 - Dec 24, 2021
- 3.2.2 - Dec 23, 2021
- 3.2.1 - Dec 02, 2021
- 3.2.0 - Nov 29, 2021
- 3.1.2 - Nov 21, 2021
- 3.1.1 - Nov 12, 2021
- 3.1.0 - Nov 09, 2021
- 3.0.8 - Oct 29, 2021
- 3.0.7 - Oct 20, 2021
- 3.0.6 - Oct 02, 2021
- 3.0.5 - Sep 25, 2021
- 3.0.4 - Sep 17, 2021
- 3.0.3 - Sep 10, 2021
- 3.0.2 - Sep 03, 2021
- 3.0.1 - Aug 27, 2021
- 3.0.0 - Aug 18, 2021
- 3.0.0-RC6 - Jul 13, 2021
- 3.0.0-RC5 - Jun 08, 2021
- 3.0.0-RC1 - Apr 15, 2021
- 2.7.5 - Oct 16, 2020
- 2.7.4 - Oct 06, 2020
- 2.7.3 - Sep 29, 2020
- 2.7.2 - Sep 18, 2020
- 2.7.1 - Sep 14, 2020
- 2.7.0 - Sep 08, 2020
- 2.6.4 - Jul 20, 2020
- 2.6.3 - Jul 14, 2020
- 2.6.2 - Jul 5, 2020
- 2.6.1 - Jun 19, 2020
- 2.6.0 - Jun 16, 2020
- 2.5.3 - May 25, 2020
- 2.5.2 - May 9, 2020
- 2.5.1 - May 3, 2020
- 2.5.0 - Apr 30, 2020
- 2.5.0-RC3 - Apr 28, 2020
- 2.5.0-RC2 - Apr 25, 2020
- 2.5.0-RC1 - Apr 15, 2020
- 2.4.2 - Feb 22, 2020
sbt-assembly
https://github.com/sbt/sbt-assembly/releases
- 2.2.0 - Mar 13, 2024
- 2.1.5 - Nov 19, 2023
- 2.1.4 - Oct 26, 2023
- 2.1.3 - Sep 17, 2023
- 2.1.2 - Sep 17, 2023
- 2.1.1 - Feb 11, 2023
- 2.1.0 - Dec 09, 2022
- 2.0.0 - Oct 17, 2022
- 2.0.0-RC1 - May 01, 2022
- 1.2.0 - Feb 12, 2022
- 1.1.0 - Aug 31, 2021
- 1.0.0 - Jun 06, 2021
- 0.15.0 - Jun 22, 2020
- 0.14.10 - Jul 11, 2019
- 0.14.9 - Oct 28, 2018

Versions of common dependencies

Joda-Time
https://github.com/JodaOrg/joda-time/releases
https://www.joda.org/joda-time/changes-report.html
- 2.12.7 - Feb 4, 2024
- 2.12.6 - Jan 6, 2024
- 2.12.5 - Mar 30, 2023
- 2.12.4 - Mar 24, 2023
- 2.12.3 - Mar 23, 2023
- 2.12.2 - Dec 17, 2022
- 2.12.1 - Oct 29, 2022
- 2.12.0 - Oct 13, 2022
- 2.11.2 - Sep 25, 2022
- 2.11.1 - Aug 25, 2022
- 2.11.0 - Aug 12, 2022
- 2.10.14 - Mar 20, 2022
- 2.10.13 - Oct 26, 2021
- 2.10.12 - Sep 29, 2021
- 2.10.11 - Sep 22, 2021
- 2.10.10 - Feb 05, 2021
- 2.10.9 - Dec 29, 2020
- 2.10.8 - Oct 23, 2020
- 2.10.7 - Oct 21, 2020
- 2.10.6 - Apr 24, 2020
- 2.10.5 - Oct 24, 2019
- 2.10.4 - Sep 20, 2019
json4s
https://github.com/json4s/json4s/tags
https://search.maven.org/search?q=org.json4s
- 4.1.0-M5 - Mar 14, 2024
- 4.1.0-M4 - Nov 18, 2023
- 4.1.0-M3 - Apr 29, 2023
- 4.1.0-M2 - Oct 14, 2022
- 4.1.0-M1 - Jan 06, 2022
- 4.0.7 - Dec 03, 2023
- 4.0.6 - Sep 28, 2022 Last version still available for Scala 2.11
- 4.0.5 - Apr 05, 2022
- 4.0.4 - Jan 22, 2022
- 4.0.3 - Jul 26, 2021
- 4.0.2 - Jul 25, 2021
- 4.0.1 - Jun 28, 2021
- 4.0.0 - May 25, 2021
- 3.7.0-RC1 - May 15, 2021
- 3.6.12 - Nov 04, 2021 Last version still available for Scala 2.10
- 3.6.11 - Mar 01, 2021
- 3.6.10 - Sep 28, 2020
- 3.6.9 - Jun 15, 2020
- 3.6.8 - May 5, 2020
- 3.6.7 - Jun 26, 2020
breeze
https://github.com/scalanlp/breeze/tags
- 2.1.0 - Aug 21, 2022 (fails)
- 2.0.1-RC2 - Dec 16, 2021
- 2.0 - Oct 04, 2021
- 1.3 - Aug 14, 2021
- 1.2 - Apr 15, 2021
- 1.1 - Aug 03, 2020
- 1.0 - Jul 27, 2019 Last version still available for Scala 2.11
requests-scala
https://github.com/com-lihaoyi/requests-scala/releases
- 0.8.2 - Apr 04, 2024
- 0.8.0 - Dec 25, 2022
- 0.7.1 - Jun 10, 2022
- 0.7.0 - Dec 11, 2021
- 0.6.9 - May 14, 2021

Various useful techniques

Checking SBT, Scala, Java version

SBT:
> sbt about
> sbt -v
> sbt sbtVersion

Scala:
> sbt scalaVersion

To see which version of Java does SBT use:
$ sbt "eval System.getProperty(\"java.version\")" "eval System.getProperty(\"java.home\")"
or in sbt shell:
sbt:subutai> eval System.getProperty("java.version")
sbt:subutai> eval System.getProperty("java.home")

scalafmt Task keys

myproject/scalafmt: Format main sources of myproject project
myproject/test:scalafmt: Format test sources of myproject project
scalafmtCheck: Check if the scala sources under the project has been formatted.
scalafmtSbt: Format .sbt and project/.scala files.
scalafmtSbtCheck: Check if the files has been formatted by scalafmtSbt.
scalafmtOnly: Format a single given file.
scalafmtAll: Execute the scalafmt task for all configurations in which it is enabled.
(By default this means the Compile and Test configurations.) (available as of v2.0.0-RC5)
scalafmtCheckAll: Execute the scalafmtCheck task for all configurations in which it is enabled.
(By default this means the Compile and Test configurations.) (available as of v2.0.0-RC5)

clean;compile;test;run

sbt> reload;+update
sbt> clean;+test:compile;+test

Run one particular main class:
sbt> runMain example.Hello

For code in test folder:
sbt> test:compile

Run one particular main class in test folder of scalaVersions project:
sbt> scalaVersions / test:runMain example.scalaVersions.TestScalaVersionsMain

Run one particular test class (of "scalatest" kind):

sbt> testOnly example.HelloSpec
or sbt> testOnly *HelloSpec

to run only the tests whose name includes the substring "hello":

sbt> testOnly *HelloSpec -- -z "hello"

See more in scalatest-in-sbt-is-there-a-way-to-run-a-single-test and in using_the_runner

tagging_your_tests

Set the SBT logging level in your build.sbt file with this setting: logLevel := Level.Debug. Or, if you’re working interactively from the SBT command line and don’t want to add this to your build.sbt file, use this syntax:> set logLevel := Level.Debug. All SBT log levels are: Debug, Info, Warning, Error.

Package

sbt:hocon> package to generate JAR in target/scala-2.12/hocon_2.12-0.1.0.jar
You can list its contents with the usual jar tvf command:

$ jar tvf target/scala-2.12/hocon_2.12-0.1.0.jar
   271 Wed Apr 29 19:15:58 PDT 2020 META-INF/MANIFEST.MF
     0 Wed Apr 29 19:15:58 PDT 2020 example/
     0 Wed Apr 29 19:15:58 PDT 2020 example/hocon/
   854 Wed Apr 29 19:14:24 PDT 2020 example/hocon/ReadConfigurationFile.class
  1020 Wed Apr 29 19:14:24 PDT 2020 example/hocon/ReadConfigurationFile$.class
   130 Wed Apr 29 19:15:58 PDT 2020 lightbend.conf

To build against all versions listed in crossScalaVersions, prefix the action to run with +. For example:
> + package

Assembly

https://github.com/sbt/sbt-assembly

Add
addSbtPlugin("com.eed3si9n" % "sbt-assembly" % "1.0.0")
to project/plugins.sbt

sbt:hocon> assembly to generate assembly JAR in
target/scala-2.12/hocon-assembly-0.1.0.jar
You can list its contents with the usual jar tvf command:

$ jar tvf target/scala-2.12/hocon-assembly-0.1.0.jar

Add test in assembly := {} to project settings to skip the test during assembly.

for version 1.0.0 and after, assembly no longer runs test by default.

To exclude Scala library

(JARs that start with scala- and are included in the binary Scala distribution) to run with scala command:

for version 1.0.0 and after:

assembly / assemblyOption ~= { _.withIncludeScala(includeScala = false) }

for version 0.15.0 and before:

assemblyOption in assembly := 
    (assemblyOption in assembly).value.copy(includeScala = false)

To make a JAR file containing only the external dependencies, type

> assemblyPackageDependency
This is intended to be used with a JAR that only contains your project:

assemblyOption in assembly := (assemblyOption in assembly).value.copy(includeScala = false, includeDependency = false)

Spark & Assembly

SBT Assembly, Spark

Publishing

The publishLocal task will publish to the “local” Ivy repository. By default, this is at $HOME/.ivy2/local/. Other builds on the same machine can then list the project as a dependency.

The publish action is used to publish your project to a remote repository. To use publishing, you need to specify the repository to publish to and the credentials to use.

scala-sbt's SBT Publishing

Sonatype OSSRH (OSS Repository Hosting)

sonatype's Producers Guide to Publishing to Central Maven Repository
sonatype's OSSRH Guide
github's Nexus Repository Publisher for GitHub Actions
jenkov's Publish JAR To Central Maven Repository with maven Jan 25, 2020
Leonard Ehrenfried's An in depth guide to deploying to Maven Central with sbt Jan 15, 2017
dzone's How to Publish Your Artifacts to Maven Central Sep 20, 2016
lightbend/config example of publishing to sonatype with sbt
circe/circe-config example of publishing to sonatype with sbt

Step-by-step

Created Sonatype JIRA account and filed JIRA issue to claim my namespace
https://issues.sonatype.org/browse/OSSRH-58349
Created a public repo called
https://github.com/whitechno/OSSRH-58349
to verify github account ownership.
com.github.whitechno has been prepared, now user(s) whitechno can:
- Deploy snapshot artifacts into repository
  https://oss.sonatype.org/content/repositories/snapshots
- Deploy release artifacts into the staging repository
  https://oss.sonatype.org/service/local/staging/deploy/maven2
- Release staged artifacts into repository 'Releases'
  Please comment on this ticket when you promoted your first release, thanks

Cross-building

https://www.scala-sbt.org/release/docs/Cross-Build.html

The underlying mechanism used to indicate which version of Scala a library was compiled against is to append _<scala-binary-version> to the library’s name. For example, the artifact name dispatch-core_2.12 is used when compiled against Scala 2.12.0, 2.12.1 or any 2.12.x version. This fairly simple approach allows interoperability with users of Maven, Ant and other build tools.

Define the versions of Scala to build against in the crossScalaVersions setting. Versions of Scala 2.10.2 or later are allowed.

Note: crossScalaVersions must be set to Nil on the root project (or all aggregating projects) to avoid double publishing.

To build against all versions listed in crossScalaVersions, prefix the action to run with +. For example:
> + test

You can use ++ <version> [command] to temporarily switch the Scala version currently being used to build the subprojects given that <version> is listed in their crossScalaVersions.

When a [command] is passed in to ++, it will execute the command on the subprojects that supports the given <version>.

Sometimes you might want to force the Scala version switch regardless of the crossScalaVersions values. You can use ++ <version>! with exclamation mark for that. For example:
> ++ 2.13.0-M5! -v

Other Special topics

Reading resources

See stackoverflow's How to read files from resources folder in Scala?

The idea is to use getClass.getResourceAsStream because it works fine when the resources are part of a jar.

val stream: java.io.InputStream = getClass.getResourceAsStream("/readme.txt")
val lines: Iterator[String] = scala.io.Source.fromInputStream(stream).getLines

Scala Worksheets in IntelliJ

"Use compile server for Scala" tick box is in
Preferences > Build, Execution, Deployment > Compiler > Scala Compiler > Scala Compile Server
you can also get to this view from the speedometer-like icon in the bottom right of IntelliJ, which can be used to Stop/Run Scala Compile Server.

"Run worksheet in the compiler process" tick box is in
Preferences > Languages & Frameworks > Scala > Worksheet (tab)
A typical way to use this feature is to do development on a single Scala version (no + prefix) and then cross-build (using +) occasionally and when releasing.

Experiments

All experiments below are with "Make project before run": On

Experiment 1
Run type: REPL
"Use compile server for Scala": On
"Run worksheet in the compiler process": On
Result: doesn't pick the change even with restart

Experiment 2
Run type: REPL
"Use compile server for Scala": On
"Run worksheet in the compiler process": Off
Result: doesn't pick the change even with restart

Experiment 3
Run type: REPL
"Use compile server for Scala": Off
Result: REPL doesn't work in this mode at all

Experiment 4
Run type: Plain
"Use compile server for Scala": On
"Run worksheet in the compiler process": On
Result: picks the change after restart

Experiment 5
Run type: Plain
"Use compile server for Scala": On
"Run worksheet in the compiler process": Off
Result: always picks the change, no need to restart

Experiment 6
Run type: Plain
"Use compile server for Scala": Off
Result: always picks the change (feels a tiny bit slower)

Final recommendations.

For dev/test/debug cycle:
"Make project before run": On
Run type: Plain
"Use compile server for Scala": On
"Run worksheet in the compiler process": Off

For exploring stable libraries:
"Make project before run": On (?)
Run type: REPL
"Use compile server for Scala": On
"Run worksheet in the compiler process": On

Slow start because of "Getting the hostname ... was slow"

Sometimes the startup time for test and run might be pretty long and you might see the following command:
[warn] Getting the hostname Olegs-MacBook-Pro was slow (18020.887197 ms). This is likely because the computer's hostname is not set. You can set the hostname with the command: scutil --set HostName $(scutil --get LocalHostName).

I found the following solution.

I used to have:

$ scutil --get HostName
Olegs-MacBook-Pro
$ scutil --get LocalHostName
Olegs-MacBook-Pro
$ time python -c 'import socket; socket.getfqdn()'
  real	0m18.134s
  user	0m0.037s
  sys	0m0.025s

Then I changed:

$ sudo scutil --set HostName Olegs-MacBook-Pro.local
    real    0m0.047s
    user    0m0.030s
    sys     0m0.012s

and then added into /etc/hosts

127.0.0.1   localhost Olegs-MacBook-Pro.local
::1         localhost Olegs-MacBook-Pro.local

SBT by example

See and try https://www.scala-sbt.org/release/docs/sbt-by-example.html

In the subutai directory create nested directories and .scala file:
src/main/scala/example/Hello.scala
In SBT shell:
sbt:Hello> clean;compile;test;run

Use Scala REPL

sbt:Hello> console
[info] Starting scala interpreter...
Welcome to Scala 2.12.7 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_171).
Type in expressions for evaluation. Or try :help.

scala> :paste
// Entering paste mode (ctrl-D to finish)

import scala.concurrent._, duration._
import gigahorse._, support.okhttp.Gigahorse
import play.api.libs.json._

Gigahorse.withHttp(Gigahorse.config) { http =>
  val baseUrl = "https://www.metaweather.com/api/location"
  val rLoc = Gigahorse.url(baseUrl + "/search/").get.
    addQueryString("query" -> "New York")
  val fLoc = http.run(rLoc, Gigahorse.asString)
  val loc = Await.result(fLoc, 10.seconds)
  val woeid = (Json.parse(loc) \ 0 \ "woeid").get
  val rWeather = Gigahorse.url(baseUrl + s"/$woeid/").get
  val fWeather = http.run(rWeather, Gigahorse.asString)
  val weather = Await.result(fWeather, 10.seconds)
  ({Json.parse(_: String)} andThen Json.prettyPrint)(weather)
}

// press Ctrl+D

// Exiting paste mode, now interpreting.

import scala.concurrent._
import duration._
import gigahorse._
import support.okhttp.Gigahorse
import play.api.libs.json._
res0: String =
{
  "consolidated_weather" : [ {
    "id" : 6446939314847744,
    "weather_state_name" : "Light Rain",
    "weather_state_abbr" : "lr",
    "wind_direction_compass" : "WNW",
    "created" : "2019-02-21T04:39:47.747805Z",
    "applicable_date" : "2019-02-21",
    "min_temp" : 0.48000000000000004,
    "max_temp" : 7.84,
    "the_temp" : 2.1700000000000004,
    "wind_speed" : 5.996333145703094,
    "wind_direction" : 293.12257757287307,
    "air_pressure" : 1033.115,
    "humidity" : 77,
    "visibility" : 14.890539250775472,
    "predictability" : 75
  }, {
    "id" : 5806299509948416,
    "weather_state_name" : "Heavy Cloud",
...

scala> :q // to quit

Use sbt-native-packager to create .zip distribution

In project/plugins.sbt add:
addSbtPlugin("com.typesafe.sbt" % "sbt-native-packager" % "1.3.4")
In build.sbt add:
.enablePlugins(JavaAppPackaging) In SBT shell:

sbt:Hello> reload
sbt:Hello> dist

In terminal shell:

> unzip -o -d /tmp/someother /tmp/foo-build/target/universal/hello-0.1.0-SNAPSHOT.zip
> /tmp/someother/hello-0.1.0-SNAPSHOT/bin/hello

run 'evicted'

[warn] There may be incompatibilities among your library dependencies; 
run 'evicted' to see detailed eviction warnings.

With some plugins (like sbt-native-packager), sbt might show eviction warning on sbt shell start, however > evicted command shows nothing.

Remember that SBT is recursive

that means, SBT uses SBT to build the SBT used to build your project.

The eviction warning you are seeing is not for your main project, but for the meta-project! You can check that by running the evicted command in the meta project using the reload plugins command. To return to the main project execute the reload return command

$ sbt
[warn] There may be incompatibilities among your library dependencies; 
run 'evicted' to see detailed eviction warnings.
sbt:Hello> evicted
[success] Total time: 0 s, completed Jan 8, 2020 11:21:26 PM


sbt:Hello> reload plugins
sbt:project> evicted
[warn] Found version conflict(s) in library dependencies; some are suspected to be binary incompatible:
[warn]  * org.scala-lang.modules:scala-xml_2.12:1.2.0 is selected over 1.1.1
[warn]      +- com.typesafe.sbt:sbt-native-packager:1.5.2 (sbtVersion=1.0, scalaVersion=2.12) (depends on 1.1.1)
[info] Here are other dependency conflicts that were resolved:
[info]  * org.scala-sbt:io_2.12:1.3.1 is selected over 1.2.2
[info]      +- com.typesafe.sbt:sbt-native-packager:1.5.2 (sbtVersion=1.0, scalaVersion=2.12) (depends on 1.2.2)
[info]  * org.scala-lang.modules:scala-parser-combinators_2.12:1.1.2 is selected over 1.1.1
[info]      +- com.typesafe.sbt:sbt-native-packager:1.5.2 (sbtVersion=1.0, scalaVersion=2.12) (depends on 1.1.1)
[success] Total time: 0 s, completed Jan 8, 2020 11:22:56 PM

sbt:project> reload return
sbt:Hello> evicted
[success] Total time: 0 s, completed Jan 8, 2020 11:25:40 PM

Is it wise to fix eviction warnings of library dependencies?

Is it a good idea to fix SBT eviction warning messages using dependencyOverrides in build.sbt as per SBT Documentation Eviction warning?

If these warnings are for dependencies you use directly in your code, you should definitely add the upgraded version to your libraryDependencies.

For evicted transitive dependencies (those dependencies only used directly by your own dependencies), it's likely best to simply leave the warnings in place. This provides documentation to you about possible incompatibilities in your dependencies, and could help you debug runtime problems that arise due to such incompatibilities.

Remember, setting dependencyOverrides merely hides the warning, it doesn't guarantee compatibility between your libraries and the version you set.