Java version of the OAuth Twitter example in the documentation
Update build from source instructions for the current code base
Add SimpleSql.map to modify defaultParser results
checkbox group helper
default server is now configurable
Added flyway plugin to Modules.md

Flyway plugin supports database migration with Flyway(http://flywaydb.org/).
play-lessc module added.
Tidied up the Play eclipse code and removed some apparently redundant logic. Also the method used to remove the scala nature from a .project file was a little fragile.
add uuid parsing

add UUID support for get values

style checking
Upgraded to fluentlenium 0.9.0

When I upgraded fluentlenium earlier, I accidentally only upgraded it
for the test dependency of the Play core project, but not the play-test
project. In fact, Play core should not have had a test dependency on
fluentlenium, since its tests don't use selenium at all.

So, I've got rid of the unnecessary test dependency (and added in
explicit dependencies on things that it brought in transitively that
were needed), and also upgraded play-test to fluentlenium 0.9.0.
Add convenience methods for changeLang(Lang lang).
Removing trailing spaces and adding trailing newlines
Fix for #1785

Make Http.Cookies extend Iterable<Http.Cookie> and add a helper to extract the cookies in play.test.Helpers.  Add tests where necessary.
Fix formspec
Use huntc idioms
Update IntegrationSpec.scala

The line browser.$("h1").first.getText.contains("Configure your 'Hello world':") does not change anything in testing. The result is ignored. This is changed by my request.
Update IntegrationSpec.scala

the result of browser.$("h1").first.getText is now used for testing . Before this change this line was useless.
Update ProductionHeroku.md

Added some text to show tailing of a heroku log; added commentary to clarify that Procfile is not actually required by Heroku.

There is another point on Heroku involving setting the build pack (see http://stackoverflow.com/questions/11510256/deploy-a-play-2-0-2-application-on-heroku):
heroku config:add BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-scala.git --app <app name here>

...but I am not sure this is required in all scenarios.
Cache the result, not the iteratee in cached action

We were caching the iteratee in the cached action, which meant that even
when the cache was hit, most of the action would still be executed.
Rather, the result should be cached.
Merge pull request #1819 from jroper/cached-action-fix

Cache the result, not the iteratee in cached action