checkbox group helper
default server is now configurable
Fix typo in production documentation

The directory which is created is 'stage', not 'staged'.
Mention the possibility to upgrade the play installation on version mismatch.

I just updated my project to play 2.2.1 and started it with my old 2.2.0 installation.
The error message

    This project uses Play 2.2.1!
    Update the Play sbt-plugin version to 2.2.0 (usually in project/plugins.sbt)

suggested a thing I wasn't interested in, instead it should have told me to update
my play installation. Both suggestions make sense.

One could even compare versions to give a more educated suggestion (detect upgrade/
downgrade), but because this should also support RCs and clever but still still short
suggestions/messages it's not done in a second and it's probably not worth the effort.
Merge pull request #1946 from fernandoacorreia/documentation

Fix typo in production documentation
Merge pull request #1964 from magro/fix-play-version-mismatch-msg

Mention the possibility to upgrade the play installation on version mismatch
Make `play new` consistent. Fixes #1927

* Make `play new` command require a parameter, the name of the project to create.
* If no parameter is given, the output now says "Use `play new foo` ..."
* It will not attempt to create something for `play new`
* Rewrite the detailedTopics/build/Build.md to adjust for this and provide more up-to-date, post 2.2 information.
* Adjust places in documentation where `play new` is mentioned.
Merge pull request #1963 from reid-spencer/master

Make `play new` consistent. Fixes #1927
Added validate pull request script
Updated documentation about gzip filters
Merge pull request #1968 from adis-me/improvements/1967-update-documentation

Updated documentation about gzip filters
Correct heroku Profile details to match new stages start script location

Per https://devcenter.heroku.com/articles/play-support the Procfile should contain:

```
web: target/universal/stage/bin/{your project name}
```
Fix typo in ScalaWS.md

s/ore/are/
Merge pull request #1972 from davidillsley/patch-1

Correct heroku Profile details to match new stages start script location
Allow to use a configured WebDriver when running with test browser.

Helpers.running and WithBrowser so far only accepted a WebDriver class
to instantiate the appropriate WebDriver.

This change allows to provide an already configured WebDriver instance.
This makes it possible to e.g. create an HtmlUnitDriver for a specific
browser version, like this:

    import org.openqa.selenium.htmlunit._
    import com.gargoylesoftware.htmlunit._
    val driver = new HtmlUnitDriver(BrowserVersion.FIREFOX_17)
    driver.setJavascriptEnabled(true)

    running(TestServer(3333), driver) { browser =>
      ..
    }

For the java version of WithBrowser it seems to be intended that for futher
customization of the browser `WithBrowser#provideBrowser` should be used:
There was no webDriver configuration possible, thus nothing is changed here.

Actually for me using the BrowserVersion.FIREFOX_17 fixed an issue
with jquery: integration tests failed with

    WebDriverException: com.gargoylesoftware.htmlunit.ScriptException: TypeError: Cannot find
    function addEventListener in object [object HTMLDocument]. (http://code.jquery.com/jquery-1.10.1.min.js#5)
Added documentation
Added test
Merge pull request #1494 from nraychaudhuri/checkbox_group_template

checkbox group helper
Merge pull request #1521 from nraychaudhuri/make_default_ebean_configurable

default ebean server is now configurable
Merge pull request #1962 from magro/running-with-webdriver

Allow to use a configured WebDriver when running with test browser