Chapter 2. Getting started
Figure 2.1. sbt’s comprehensive help menu
Chapter 3. Core concepts
Figure 3.1. Configuring the name of the preowned-kittens build file. This sets the project name to the string literal “preowned-kittens”.
Figure 3.2. Settings with sbt defaults
Figure 3.3. Overriding settings
Figure 3.4. To write a test for your new project, you added the specs2 testing library.
Figure 3.5. Appending to settings
Figure 3.6. Adding a common library to your preowned-kittens build
Figure 3.7. You can access the value of another setting using the value method. In this example, the initialization receives the value of the version setting. This expression generates a new ModuleID with that setting.
Figure 3.8. The library shares the same organization as the website, so you use it when depending on the core library.
Figure 3.9. Mapping setting dependencies to a spreadsheet
Figure 3.10. To create a new task in sbt, you first need to create a new key that can store the value of the Git commit.
Figure 3.11. After defining a new key to contain the Git SHA, you can define a new setting that will grab the value of the SHA and place it in the setting.
Figure 3.12. Creating a task that generates the properties file that contains the Git version
Figure 3.13. You need to tell sbt to include this properties file in the runtime classpath for your website. To do that, you can use the resourceGenerators key.
Figure 3.14. Configurations as worksheets