We are very pleased to announce the availability of play 2.1-RC1!
Migration guide: https://github.com/playframework/Play20/wiki/Migration
Lighthouse milestone: https://play.lighthouseapp.com/projects/82401-play-20/milestones/current
How to install:
1) read the migration guide
2) download package from http://www.playframework.org/download
3) change project/build.properties to 0.12.1 and the play version in project/plugins.sbt to 2.1-RC1
Let us know if you have questions or run into problems.
HelloI have migrated to 2.1 Rc1 from 2.0.4 but getting several errors with my project src...where is the java doc located for 2.1 ?For example this error ..even though I explicitly set to akka.dispatch.Future still complainserror: incompatible types[error] akka.dispatch.Future<Object> future = Patterns.ask(CometActorSystem.getPresenceRemoteActorRef(),message,timeout);[error] ^[error] required: akka.dispatch.Future<Object>[error] found: scala.concurrent.Future<Object>
Thanks, I was able to resolve but getting run time errrosSo I am wondering what should be the Akka version in build.scalaEarlier with Play 2.0.4 I had this...since Now I am migrating to 2.1 RC1 what should this be...
val appDependencies = Seq(// Add your project dependencies here,"com.typesafe.akka" % "akka-remote" % "2.0.2")I am new Play and Akka...Just started 2-3 weeks back...now migrating to 2.1 for cookie issue with Async
Hi,What happened to the "eclipsify" command? Is there another way to create eclipse files for a new project?Rob
Hi Peter,Many thanks for posting RC1 - I've upgraded successfully but have a little gripe that I'd like to share with you.A while back, I seem to remember discussion about running out of memory/maxing the CPU whilst running tests.The problem that I am having at the moment and I would love to be confirmed that this is not just me is that when I repeatedly run 'test' from within the play console, eventually I notice my fans get continually faster until I quit the process.
I upgraded to Play 2.1-RC1 and I get the below compile time error:value message is not a member of Option[play.api.data.FormError]Below is the line where above error is thrown:<p class="error">@form.globalError.message</p>Any idea folks?
I upgraded to Play 2.1-RC1 and I get the below compile time error:value message is not a member of Option[play.api.data.FormError]Below is the line where above error is thrown:<p class="error">@form.globalError.message</p>
Any idea folks?
On Sunday, 25 November 2012 14:46:22 UTC-5, mirkoadari wrote:
On Sunday, November 25, 2012 at 9:36 PM, mirkoadari wrote:
How does scheduler API work for Java with 2.1? Akka.scheduler().schedule() expects an ExecutionContext instance.
On Tuesday, November 20, 2012 at 2:39 PM, Ondřej Kroupa wrote:
Anybody got any auhenticate module working with this release? I have tried play-authenticate and securesocial without success.
Hi Peter,thanks a lot for play! 2.1 RC.We are new to play!, but like to use it for a university project.
Currently we start off and think about directly using 2.1 RC instead of 2.0.4.Could you or any experienced play contributor please tell, whether we have to expect incompatible API changesbetween the RC and the final release of 2.1?
Hi All,I've enjoyed using play 2.1-RC1 for the last week. When I deploy to heroku with 2.1-RC1 the compiled slug size is 120MB (up from 54MB in play 2.0.x). I'm using the build pack from https://github.com/heroku/heroku-buildpack-scala.git. The slug size is not causing problems at the moment. However heroku recommends that slug sizes should be less than 100MB. Any ideas?Cheers,Mark
Put it in public/stylesheets/
How did you fix your imports? I have errors relating to forms.
On Friday, 21 December 2012 23:48:28 UTC, Brian Hanafee wrote:The migration guide suggests adding javaCore, javaJdbc and javaEbean to appDependencies. It mentions as an aside that it's no longer necessary to specify mainLang because enabling javaCore is sufficient to enable Java support. It then describes the move of play.mvc.Controller#form() to play.data.Form#form(). When I recompiled after upgrading, I had a bunch of compilation errors related to forms, so dove into those changes to figure out what had gone wrong and fix my imports. It would have save me a ton of time if the migration guide had mentioned that, unrelated to moving the form() methods, adding javaCore to the path of a Scala project breaks it.
Does play 2.1 (scala) have native support for Slick?
i cannot get the
static Form<Task> taskForm = form(Task.class);