Documentation

You are viewing the documentation for the 2.2.x release series. The latest stable release series is 3.0.x.

§About SBT Settings

§About sbt settings

The build.sbt file defines settings for your project. You can also define your own custom settings for your project, as described in the sbt documentation. In particular, it helps to be familiar with the settings in sbt.

To set a basic setting, use the := operator:

confDirectory := "myConfFolder"     

§Default settings for Java applications

Play defines a default set of settings suitable for Java-based applications. To enable them add the play.Project.playJavaSettings set of settings to your build.sbt file. These settings mostly define the default imports for generated templates e.g. importing java.lang.* so types like Long are the Java ones by default instead of the Scala ones. play.Project.playJavaSettings also imports java.util.* so that the default collection library will be the Java one.

§Default settings for Scala applications

Play defines a default set of settings suitable for Scala-based applications. To enable them add the play.Project.playScalaSettings set of settings to your build.sbt file. These default settings define the default imports for generated templates (such as internationalized messages, and core APIs).

§Play project settings with their default value

When you define your sbt project using the default settings explained above, use sbt’s settings command via the play console for your project (the console is obtained by invoking the play command from the command line). You can then further show the value of a setting by using the sbt show command e.g. show name will output the project’s name.

Next: Managing library dependencies


Found an error in this documentation? The source code for this page can be found here. After reading the documentation guidelines, please feel free to contribute a pull request. Have questions or advice to share? Go to our community forums to start a conversation with the community.