Play 2.3.1 released!

1,970 views
Skip to first unread message

James Roper

unread,
Jun 25, 2014, 1:03:55 AM6/25/14
to play-framework
Hi all,

Play 2.3.1 has been released!  This release is primarily a bug fix release.  The issues fixed include:
  • 2936 Fixed duplicate entry error when multiple sub projects depend on the same webjar
  • 2967 Ensure SecurityHeadersFilter constructor doesn’t prevent Application from starting
  • 2973 Use minified assets in production automatically if they exist
  • 2986 Fixed deadlock in tests
  • 3012 Update to latest Twirl
  • 3044 Provided JavaScript literal binder for Assets
  • 3050 Fixed reverse routing routes priority
  • 3057 Fixed excessive reloading
  • 3064 Fixed HEAD support in CSRF filter
  • 3066 Upgraded to Netty 3.9.2 to fix a security vulnerability in the SSL support
For a full list of what was changed, please see here.

Upgrade notes
  • The behaviour of the Assets reverse router has changed, if minified versions of assets exist, it now returns a URL for those instead. To disable this behaviour, set assets.checkForMinified=true in application.conf.
  • A change to the SecurityHeadersFilter constructor breaks binary compatibility. This was done because the old constructor signature could not be used for its intended purpose without breaking it.
Thanks to everyone in the community who helped by reporting and/or fixing issues.

Enjoy!

--
James Roper
Software Engineer

Typesafe – Build reactive apps!
Twitter: @jroper

Artem Kalinovskiy

unread,
Jun 25, 2014, 2:36:40 AM6/25/14
to play-fr...@googlegroups.com
Hi James,

Unfortunately this release doesn't include batch sql fixes - https://github.com/playframework/playframework/pull/3016 .
At the moment we are forced to use a custom build with that fixes.
When are you going to release anorm with working batch sql functionality?

Mateusz Szczap

unread,
Jun 25, 2014, 3:45:05 AM6/25/14
to play-fr...@googlegroups.com
Actually I have to defend James and Typesafe. I think they are limited in their capacity and are working on this voluntarily, also the more you include in point release the more probability for defects and instability.
Message has been deleted

Artem Kalinovskiy

unread,
Jun 25, 2014, 4:04:54 AM6/25/14
to play-fr...@googlegroups.com
Totally agree! And I have no complaints about their work. Without a doubt play is a wonderful framework! 
But I suppose that batch sql is an important part of anorm. Perhaps there is an opportunity to release only anorm version with fixes.

James Roper

unread,
Jun 25, 2014, 8:24:06 AM6/25/14
to play-framework
I wasn't aware of that regression.  We'll get it backported for 2.3.2.


On Wed, Jun 25, 2014 at 6:03 PM, Artem Kalinovskiy <artem.ka...@gmail.com> wrote:

Totally agree! And I have no complaints about their work. Without a doubt play is a wonderful framework! 
But I suppose that batch sql is an important part of anorm. Perhaps there is an opportunity to release only anorm version with fixes.

Totally agree


On Wednesday, June 25, 2014 11:45:05 AM UTC+4, Mateusz Szczap wrote:

--
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.
For more options, visit https://groups.google.com/d/optout.

Artem Kalinovskiy

unread,
Jun 25, 2014, 8:29:03 AM6/25/14
to play-fr...@googlegroups.com
Thanks for the reply, James.


On Wednesday, June 25, 2014 4:24:06 PM UTC+4, James Roper wrote:
I wasn't aware of that regression.  We'll get it backported for 2.3.2.
On Wed, Jun 25, 2014 at 6:03 PM, Artem Kalinovskiy <artem.ka...@gmail.com> wrote:

Totally agree! And I have no complaints about their work. Without a doubt play is a wonderful framework! 
But I suppose that batch sql is an important part of anorm. Perhaps there is an opportunity to release only anorm version with fixes.

Megazord

unread,
Jun 25, 2014, 8:55:56 PM6/25/14
to play-fr...@googlegroups.com
Awesome! Thanks for the good work, guys.

Megazord

unread,
Jun 25, 2014, 9:21:27 PM6/25/14
to play-fr...@googlegroups.com
By the way, I think I got a minor regression with this release. After upgrading (just changing plugin version to 2.3.1 and also sbt-web to 1.0.2), the assets urls are being generated with a extra "/". With the following route:

GET     /assets/v/*file    controllers.Assets.versioned(path="/public", file: Asset)


I get urls like this:

/assets/v//stylesheets/7647f1e06b2f5cdf370bc10374ebf3e6-bootstrap.min.css

Notice the extra "/" after "/assets/v". The route works both with and without the extra slash, but of course this is bad when considering cache (since it is a new url). Should I open an issue?

Best,

Steven Marcus

unread,
Jun 25, 2014, 9:28:37 PM6/25/14
to play-fr...@googlegroups.com

https://github.com/playframework/playframework/commit/6b8bad5b7f20a665381415927ce057d0ef59a6cd

fixes the problem.

Until 2.3.2 is available, I was hoping to work around the issue by not using minified assets?

thanks,
Message has been deleted

Marius Bozem

unread,
Jun 30, 2014, 3:53:11 AM6/30/14
to play-fr...@googlegroups.com

Since the update I'm getting some compile warning about my routes file. Everything still seems to work just fine and I don't know how to resolve these warnings. Could someone please give me a little hint whats wrong here? Thanks in advance!


[warn] /conf/routes:83: patterns after a variable pattern cannot match (SLS 8.1.1)
[warn] If you intended to match against parameter page of method index, you must use backticks, like: case `page` =>
[warn] GET   /trainer/singletraining/availability/:page            @controllers.trainer.singletraining.AvailabilityCtrl.index(page: Integer)
[warn] /conf/routes:82: unreachable code due to variable pattern 'page' on line 1127
[warn] If you intended to match against parameter page of method index, you must use backticks, like: case `page` =>
[warn] GET   /trainer/singletraining/availability                  @controllers.trainer.singletraining.AvailabilityCtrl.index(page: Integer = 1)
[warn] /conf/routes:82: unreachable code
[warn] GET   /trainer/singletraining/availability                  @controllers.trainer.singletraining.AvailabilityCtrl.index(page: Integer = 1)


Relevant part of the routes file:

Line 82:
GET   /trainer/singletraining/availability                  @controllers.trainer.singletraining.AvailabilityCtrl.index(page: Integer = 1)

Line 83:
GET   /trainer/singletraining/availability/:page            @controllers.trainer.singletraining.AvailabilityCtrl.index(page: Integer) 
 

James Roper

unread,
Jun 30, 2014, 4:18:38 AM6/30/14
to play-framework
On Mon, Jun 30, 2014 at 5:53 PM, Marius Bozem <marius...@gmail.com> wrote:

Since the update I'm getting some compile warning about my routes file. Everything still seems to work just fine and I don't know how to resolve these warnings. Could someone please give me a little hint whats wrong here? Thanks in advance!

Known issue, already fixed, we hope to release 2.3.2 later this week.

James Ward

unread,
Aug 23, 2014, 9:40:45 PM8/23/14
to play-fr...@googlegroups.com
Did this make it into 2.3.2 or 2.3.3?  I'm using 2.3.3 and still seeing this warning.

-James

James Roper

unread,
Aug 25, 2014, 1:33:35 AM8/25/14
to play-framework
On Sun, Aug 24, 2014 at 11:40 AM, James Ward <jlwa...@gmail.com> wrote:
Did this make it into 2.3.2 or 2.3.3?  I'm using 2.3.3 and still seeing this warning.

Make sure you do a clean build.

What exact warning are you seeing?
 
-James

On Monday, June 30, 2014 2:18:38 AM UTC-6, James Roper wrote:
On Mon, Jun 30, 2014 at 5:53 PM, Marius Bozem <marius...@gmail.com> wrote:

Since the update I'm getting some compile warning about my routes file. Everything still seems to work just fine and I don't know how to resolve these warnings. Could someone please give me a little hint whats wrong here? Thanks in advance!

Known issue, already fixed, we hope to release 2.3.2 later this week.

--
James Roper
Software Engineer

Typesafe – Build reactive apps!
Twitter: @jroper

--
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.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages