Use javaOptions
sbt setting in Build.scala or build.sbt to pass jvm options to tests e.g.
- statically:
javaOptions in Test ++= Seq("-Dconfig.file=conf/staging.conf")
or
Use javaOptions
sbt setting in Build.scala or build.sbt to pass jvm options to tests e.g.
javaOptions in Test ++= Seq("-Dconfig.file=conf/staging.conf")
or
This gist provides a simple example of how to use Play's WS library in a standalone application (external to Play).
build.sbt - SBT build file that includes the WS library WSStandaloneTest.scala - A simple example that utilizes WS to invoke an HTTP GET request
Please write good git commit messages. A good commit message | |
looks like this: | |
Header line: explain the commit in one line (use the imperative) | |
Body of commit message is a few lines of text, explaining things | |
in more detail, possibly giving some background about the issue | |
being fixed, etc etc. | |
The body of the commit message can be several paragraphs, and |
// Actions in controllers will be defined like this: | |
def create = ComposedAction.async(parse.tolerantJson) { implicit request => ... } | |
// instead of this: | |
def create = Action.async(parse.tolerantJson) { implicit request => ... } |