Merge pull request #1873 from wsargent/818-fix-null-querystring-binder

Provide empty string default for bindableString.unbind
Merge pull request #1870 from baloo/bugfixes/1076-Thread-safety-vars

[#1076] thread safety vars
Merge pull request #1859 from pkrcah/fix-1858

Protect directory names in "play" script with quotes. Fixes #1858.
Replace play{scala,java}Settings reference with fully qualified class path
Merge pull request #1868 from brikis98/filter-all-requests

Filters should be executed on every single request
Merge pull request #1852 from brikis98/java-options-#1776

The play run and start commands now respect javaOptions
Add some best practices for compilation speed suggested by Mark Harrah
Merge pull request #1872 from benmccann/compilation-speed-docs

Add some best practices for compilation speed suggested by Mark Harrah
Merge pull request #1863 from jroper/1863-sbt-plugin-sources

no sources published for sbt-plugin
Akka migration guide for 2.2

Fixes #1718

Added link to Akka 2.1 to 2.2 migration guide from the 2.2 migration
guide.
Added a note regarding the retirement of extending the sbt namespace.
Merge pull request #1718 from jroper/1718-akka-migration

[2.2 migration] Add a link to Akka 2.2 migration guide
[#983] Ask user if he is using a case class
[#1109] Rename functions to get*Seq
[#1449] Test badly encoded request
[#1449] Handle misformated cookies
[#1449] Add debug message
Make sure specs tests are run by Specs2 not JUnit

When a Specs2 test has an @RunWith(classOf[JUnitRunner]) annotation then
it can be run by either JUnit or Specs2. But we want the tests to be run
by Specs2, so we tell junit-interface to ignore that particular runner.
Unfortunately, if SBT may ask JUnit to run the test. If it does so, then
the test will be executed but the result will be ignored by SBT.

This change is a hack to make sure that SBT always asks Specs2 to run the
test, never JUnit. We can make sure Specs2 is preferred by adding Specs2
as the last entry in the testFrameworks SBT setting. Since SBT runs
frameworks in reverse order, it will always run Specs2 before JUnit.
The commonjs functionality is now optional and specified by a new "commonJs" option.

Unfortunately the commonjs functionality is ill-documented and difficult to get working on Windows at least. Hence its relegation to an option.
Merge pull request #1885 from baloo/bugfixes/1449-malformed-cookies

Bugfixes/1449 malformed cookies