Play 2.6.10 released!

[Greg Methvin]

The Play Team is pleased to announce the release of Play Framework 2.6.10. This is the latest stable release of Play.

Getting Play

• To start a new project, visit www.playframework.com/download.
• To upgrade an existing Play 2.6 project, edit your project/plugins.sbt file and set the sbt-plugin to 2.6.10.
• To update an older Play project, take a look at the Migration Guide.

Changelog

See the full list of changes and the 2.6.10 milestone on GitHub. The changes include several backwards-compatible bug fixes.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Play core team's efforts. Lightbend offers commercial support for Play.

Special thanks to the following contributors who helped with this release: Tim Moore, Greg Methvin, Ignasi Marimon-Clos, Marcos Pereira, Rich Dougherty.

--

Greg Methvin

Tech Lead - Play Framework

Lightbend, Inc.

[Enrico Morelli]

Thanks for your wonderful work.

 A simple stupid think, can you stick the announce? I used to see the new releases announce as first post while in this case I loose the announce.

Thanks again

[jcstritt]

Thank for your work, but why always this warning already present in version 2.6.9 ?

[Greg Methvin]

Unfortunately the fix for that didn't make it into 2.6.10. I just submitted a fix here: https://github.com/playframework/playframework/pull/8118

You can remove the log by adding to your logback.xml: <logger name="application" level="ERROR" />

That's not an ideal fix if you are using the static Logger methods, since those all share the "application" logger, but ideally you should be creating a new logger instance for each class you are using it in (e.g. private val logger = Logger(getClass)). If you are following that best practice there should be no problem with muting the "application" log messages.

On Fri, Dec 22, 2017 at 4:40 PM, jcstritt <jcst...@gmail.com> wrote:

Thank for your work, but why always this warning already present in version 2.6.9 ?

--
You received this message because you are subscribed to the Google Groups "Play Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framework+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/play-framework/62e8153a-56ad-4665-896b-75c1a88b7838%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Thibault Meyer]

Hope it will be removed in the next release or lowered to debug / trace level

Le vendredi 22 décembre 2017 23:16:37 UTC+1, Greg Methvin a écrit :

Unfortunately the fix for that didn't make it into 2.6.10. I just submitted a fix here: https://github.com/playframework/playframework/pull/8118

You can remove the log by adding to your logback.xml: <logger name="application" level="ERROR" />

That's not an ideal fix if you are using the static Logger methods, since those all share the "application" logger, but ideally you should be creating a new logger instance for each class you are using it in (e.g. private val logger = Logger(getClass)). If you are following that best practice there should be no problem with muting the "application" log messages.

On Fri, Dec 22, 2017 at 4:40 PM, jcstritt <jcst...@gmail.com> wrote:

Thank for your work, but why always this warning already present in version 2.6.9 ?

--
You received this message because you are subscribed to the Google Groups "Play Framework" group.

To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/play-framework/62e8153a-56ad-4665-896b-75c1a88b7838%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.