Add SBT cookbook in the documentation
Automatically start things in WithXxx helper classes
Update code to leverage the new way of using WithXxx helper classes
Wrapped the TimeoutException in the unchecked exception

Wrapped the TimeoutException of `Promise#get()` in the unchecked exception for timeout handling.
fix image tag example
Update play-java template to use new Twirl API
Added favicon to play-2.3-highlights template to fix 404
Changes required in support of sbt-web 1.0.0-RC1
Incorporated asset fingerprinting
Merge pull request #2778 from huntc/sbt-web-100RC1

Sbt web 100 rc1
A slight refinement in order to exclude less files.
Add migration notes for templates
Fix up missing JavaScript in templates

We don't need JQuery, so instead I added in a dummy
example JavaScript file
Merge pull request #2785 from pvlugter/twirl-migration-notes

Add migration notes for templates
Merge pull request #2786 from richdougherty/template-fixes

Misc template fixes
Remove the scalaVersion setting from the Play sbt plugin

Play 2.3 will support multiple versions of Play so it's no longer
appropriate for the sbt plugin to provide a setting with a fixed
Scala version. The setting has been removed. Instead the Play
templates will provide an explicit scalaVersion setting instead.

Change all build file to accept the scala.version system property
to configure the version of Scala that they use. Most build files
default to Scala 2.10.4, but the build file that generates the
Play templates will generate build.sbt files with a default value
of 2.11.0.

With this commit, runtests works with Scala 2.10.4, but fails on
the documentation tests when run with Scala 2.11.0. I haven't
fixed the documentation tests as part of this commit because this
commit is blocking 2.3.
Update to twirl 1.0.0-RC1
Merge pull request #2788 from richdougherty/play-scala-version

Remove the scalaVersion setting from the Play sbt plugin
Merge pull request #2789 from pvlugter/twirl-rc1

Update to twirl 1.0.0-RC1
Fixed 2.11 documentation build

Also fixed the scala custom field constructors documentation, it was a
mess, polluted the global namespace, and didn't have any tests to verify
that the docs did what they said they did.