Play framework 1.0 (now in maintenance mode): 1.2.3
Evolutions checks evolution state on every request in prod mode (Performance issue)evolutions performance ✓ resolved
Docs: add application.conf referenceconfiguration documentation ✓ resolved
Allow play configuration to read environment variablesno tags ✓ resolved
Add OnApplicationStop annotation and implement the logiccandidate123 ✓ resolved
When using SSL, Play always requests client authenticationcandidate123 ✓ resolved
Built-in Tags documentation page enhancement: form tagdocumentation ✓ resolved
Add a "silent" option to hide Play logo in python scriptsno tags ✓ resolved
Pull request: Bug fix: Port numbers in the request URL should not affect routingno tags ✓ duplicate
play deps: force copyno tags ✓ resolved
Broken 'JQuery Tools Expose' linkdocumentation ✓ resolved
Add play! sources in IntelliJ configurationcandidate123 ✓ resolved
Include a patched postgres jdbc driverno tags ✓ resolved
VCS documentation is not up to datedocumentation ✓ resolved
Typo in Intellij templatecandidate123 ✓ resolved
Add play version commandno tags ✓ resolved
Describe support/ directory tools for Eclipse, vim and Textmatedocumentation ✓ resolved
Allow JVM arguments in the evolutions commandno tags ✓ resolved
play auto-test should return errorcode=1 if tests failcandidate123 ✓ resolved
Add documentation about howto write checksdocumentation ✓ resolved
Docs: add Cobertura installation to tutorial 'Completing the application tests'documentation tutorial ✓ resolved
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the http://www.playframework.org website.
Source code is hosted on githubCheck out our repository at http://github.com/playframework/play
Contributing, creating a patchPlease read the contributor guide
Reporting Security VulnerabilitiesSince all bug reports are public, please report any security vulnerability directly to guillaume dot bort at gmail dot com.
Creating a bug reportBug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.
Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.
Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.