Play 2.1.1-RC1 is available

756 views
Skip to first unread message

James Roper

unread,
Mar 19, 2013, 11:59:06 PM3/19/13
to play-fr...@googlegroups.com
We're pleased to announce the release of Play 2.1.1-RC1.  This is a bugfix release, that addresses the following issues:
  • Reverted changes to multipart/form-data API so that no file submitted can be easily detected
  • Reverse router now escapes String path parameters
  • Invalid escape combinations in the query string and path now return 400 errors
  • Routes files that only contain includes now compile
  • Javadoc generation is now working
  • Compiled assets are no longer part of watched sources
  • Fixed some compilation problems on Windows
  • Improved routes helpers implementation
This release can be downloaded from 


A number of the bugfixes were contributed by the community, for which we are very grateful.

Enjoy!

James Roper

adel alfar

unread,
Mar 22, 2013, 11:27:28 AM3/22/13
to play-fr...@googlegroups.com
Thanks to all play2.X team!

Peter Empen

unread,
Mar 23, 2013, 4:45:46 AM3/23/13
to play-fr...@googlegroups.com
Awesome!
Will Play 2.1.1 be based on Scala 2.10.1?
Peter

Myyk

unread,
Mar 23, 2013, 2:49:43 PM3/23/13
to play-fr...@googlegroups.com
I was burned by the multipart/form-data API change, I'm happy to see that the fix is going out so that it shouldn't happen to anyone else.  Thanks for the fixes!

James Roper

unread,
Mar 25, 2013, 12:39:25 AM3/25/13
to play-framework
On Sat, Mar 23, 2013 at 7:45 PM, Peter Empen <empen...@gmail.com> wrote:
Awesome!
Will Play 2.1.1 be based on Scala 2.10.1?
 
Play 2.1.1 is compiled against Scala 2.10.0, but runs just fine with Scala 2.10.1, just set scalaVersion := "2.10.1" in your build settings.  playframework.com is actually currently running on 2.1.1-RC1 with Scala 2.10.1.

The Scala team are being very careful with the 2.10.x series to ensure backwards compatibility, and SBT now only publishes artifacts against the major number, not the minor number, so all 2.10.x releases should work fine with all versions of Play 2.1.x, in theory :)



Peter

--
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/groups/opt_out.
 
 



--
James Roper
Software Engineer

Typesafe - The software stack for applications that scale
Twitter: @jroper

Adis

unread,
Mar 25, 2013, 5:27:15 PM3/25/13
to play-fr...@googlegroups.com
Is it correct to put the following into plugins.sbt:

addSbtPlugin("play" % "sbt-plugin" % "2.1.1-RC1")



Op woensdag 20 maart 2013 04:59:06 UTC+1 schreef James Roper het volgende:

James Roper

unread,
Mar 26, 2013, 2:15:57 AM3/26/13
to play-fr...@googlegroups.com
On Tuesday, March 26, 2013 8:27:15 AM UTC+11, Adis wrote:
Is it correct to put the following into plugins.sbt:

addSbtPlugin("play" % "sbt-plugin" % "2.1.1-RC1")

Yes.

Peter Empen

unread,
Apr 22, 2013, 10:19:00 AM4/22/13
to play-fr...@googlegroups.com

Play 2.1.1 is compiled against Scala 2.10.0, but runs just fine with Scala 2.10.1, just set scalaVersion := "2.10.1" in your build settings.  playframework.com is actually currently running on 2.1.1-RC1 with Scala 2.10.1.
 
After I configured

  lazy val web = play.Project(
      name = "web",
      applicationVersion = appVersion
  ).settings(
    scalaVersion := "2.10.1",
    ...
  )

the Play console still outputs "play! 2.1.1 (using Java 1.7.0_05 and Scala 2.10.0), http://www.playframework.org" but

[web] $ scala-version
[info] 2.10.1

So which is true?

Peter Empen

unread,
Apr 22, 2013, 10:26:48 AM4/22/13
to play-fr...@googlegroups.com
It seems that the displayed version is wrong...

Nilanjan Raychaudhuri

unread,
Apr 22, 2013, 12:11:58 PM4/22/13
to play-fr...@googlegroups.com
It picks the version that is used to build Play

Nilanjan, Developer & Consultant
Typesafe Inc.
Twitter: @nraychaudhuri
Reply all
Reply to author
Forward
Message has been deleted
0 new messages