Compile, or compile not. There's no warning. Two of my favorite Scala compiler flags lately are "-Xlint" and "-Xfatal-warnings".
Here is an example setting that can be used with subprojects:

ThisBuild / organization := "com.example"
ThisBuild / version      := "0.1.0-SNAPSHOT"
ThisBuild / scalaVersion := "2.12.6"
 
lazy val commonSettings = List(
  scalacOptions ++= Seq(
    "-encoding", "utf8",
    "-deprecation",
    "-unchecked",
    "-Xlint",
    "-feature",
    "-language:existentials",

git gone is a custom git command that I wrote based on Erik Aybar's Git Tip: Deleting Old Local Branches. I'm not comfortable with Bash scripting, so it took me some Googling and Stackoverflowing, but hopefully it does the job. Save the source at the end of this page as git-gone in ~/bin or wherever you keep your local scripts.

To read how to use it type in git gone:

$ git gone
usage: git gone [-pndD] [<branch>=origin]
OPTIONS
  -p  prune remote branch
  -n  dry run: list the gone branches
  -d  delete the gone branches
  -D  delete the gone branches forcefully
 
EXAMPLES
git gone -pn  prune and dry run
git gone -d delete the gone branches

Spotify: https://open.spotify.com/user/1235450353/playlist/5US2KVLXPDrsB1C3IikMpT...
YouTube: https://www.youtube.com/playlist?list=PLSUh6oJ5ZotVUgp0rFjOJPKyVoFQMEUzo

• First Flight - Kaitlyn Aurelia Smith
• Vind - Christian Löffler, Mohna
• Heptapod B - Jóhann Jóhannsson
• Bad Blood - SBTRKT Remix - Nao
• Glasir - Telefon Tel Aviv Remix - These Hidden Hands
• A Parallel Life - Ocoeur
• Object Unknown - Kool Keith
• Airships Fill the Sky - Morgan Packard
• Retrograde - James Blake
• Nowhere - Crazy P's Heatwave Mix - Aquanote, Zoe Ellis

The foundation of rich console application is based on physical terminal machines like VT100 from the 1970s, and ANSI X3.64 control sequences that standarized the byte sequence to control the cursor, text formats, etc. Modern terminal applications emulate the behaviors of these terminals.

Thus, if we can assume a good terminal app, all we need is an ability to println(...) the control sequences and listen for the standard input to write a rich console app. This should be possible in almost any programming language.

Wrote sbt 1.2.0 on Lightbend Tech Hub blog.

Whether you want to try using OpenJDK 11-ea, GraalVM, Eclipse OpenJ9, or you are stuck needing to build using OpenJDK 6, jabba has got it all. jabba is a cross-platform Java version manager written by Stanley Shyiko (@shyiko).

AdoptOpenJDK 8 and 11

Here's how we can use jabba on Travis CI to cross build using AdoptOpenJDK 8 and 11:

sudo: false
dist: trusty
group: stable
 
language: scala
 
scala:
  - 2.12.7
 
env:
  global:
    - JABBA_HOME=/home/travis/.jabba
 
matrix:

Spotify: https://open.spotify.com/user/1235450353/playlist/4jqNCyUylGh9zCYt0JHqEv...
YouTube: https://www.youtube.com/playlist?list=PLSUh6oJ5ZotVoTIXr6OBeLuUSor-PDN_p

• The Seed - ANIMA!
• Looped - Kiasmos
• Naive - RKCB
• Making Distractions - Kllo
• Lights - YOSIE, LO
• CR-V - Cuco
• Arisen My Senses - Björk
• Hush - Tourist
• You and Me - Shallou
• Last Day… - Shallou
• Life, Life (Andy Stott Remodel) - Ryuichi Sakamoto
• Nix - Dawn of Midi
• A Meaningful Moment Through a Meaning(less) Process - Stars Of The Lid
• Obfuse - Floating Points

I wanted give Expecty a try, so I forked the repo to eed3si9n/expecty, added sbt build, patched up the code so it works with 2.10, 2.11, 2.12, and 2.13.0-M4, sent a few pull requests upstream, changed the package name, and published my fork to Maven Central:

libraryDependencies += "com.eed3si9n.expecty" %% "expecty" % "0.11.0" % Test

and for Scala.JS and Scala Native:

libraryDependencies += "com.eed3si9n.expecty" %%% "expecty" % "0.11.0" % Test

Here's how we can use this:

scala> import com.eed3si9n.expecty.Expecty.assert
import com.eed3si9n.expecty.Expecty.assert
 
scala> assert(a * b == 7)
java.lang.AssertionError:
 
assert(a * b == 7)
       | | | |
       1 3 3 false
 
  at com.eed3si9n.expecty.Expecty$ExpectyListener.expressionRecorded(Expecty.scala:25)
  at com.eed3si9n.expecty.RecorderRuntime.recordExpression(RecorderRuntime.scala:34)
  ... 38 elide

As you can see, you get a nicer error message automatically.

Source dependencies is one of features that existed in sbt since ever, but hasn't been documented well.

Using sbt-sriracha, we can define a hybrid dependency to µTest as follows:

lazy val utestJVMRef = ProjectRef(uri("git://github.com/eed3si9n/utest.git#5b19f47c"), "utestJVM")
lazy val utestJVMLib = "com.lihaoyi" %% "utest" % "0.6.4"
 
lazy val root = (project in file("."))
  .sourceDependency(utestJVMRef, utestJVMLib)
  .settings(
    name := "Hello world",
    testFrameworks += new TestFramework("utest.runner.Framework"),
  )

Now using these changes I can run custom µTest on Scala 2.13.0-M4.

Yesterday I wrote about cross JVM testing using Travis CI.

testing Scala apps on macOS using Travis CI

Here's how we can test Scala apps on macOS using Travis CI. This is adapted from Lars and Muuki's method: Testing Scala programs with Travis CI on OS X

dist: trusty
 
language: scala
 
matrix:
  include:
    ## build using JDK 8, test using JDK 8
    - script: