playframework-2.3

The answer to my problem is probably very simple and stupid but, can't find it by myself so far. Using Play Framework, emberjs and FluentLenium, I wrote a very simple functional test but can't make it works under IntelliJ IDEA 13 . For some reason, every assets located in the public/ and app/ folders are not found when I run the test with IntelliJ. Here's my code : import org.junit.Test; import play.libs.F.Callback; import play.test.TestBrowser; import play.test.WithApplication; import static org.fest.assertions.Assertions.assertThat; import static play.test.Helpers.*; public class

Once I run 'sbt compile' on a 2.3 play project, I can't use 'sbt compile' to compile any Play 2.2.x projects anymore. This is the error when I run sbt command. [info] Loading project definition from /Users/macbookpro/playproject/project [error] java.lang.NoClassDefFoundError: play/Play$ [error] Use 'last' for the full log. Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? I just had this same issue. In my case I was using Play 2.4, but it's probably the same cause. I had run activator ui in my project directory accidentally. It created a project/play-fork-run.sbt file which is for

Edit: There is a related issue being discussed on Github but in another mode of deployment (Typesafe Activator UI and not Docker). I was trying to simulate a system reboot in order to verify the Docker restart policy which declares to be able to re-run containers in the correct order. I have a Play framework application written in Java. The Dockerfile looks like this: FROM ubuntu:14.04 # # [Java8, ...] # RUN chmod +x /opt/bin/playapp CMD ["/bin/bash"] I start it using $ docker run --restart=always -d --name playappcontainer "./opt/bin/playapp" . When I $ service docker stop && service docker

Scala 2.11 is out and the 22 fields limit for case classes seems to be fixed ( Scala Issue , Release Notes ). This has been an issue for me for a while because I use case classes to model database entities that have more than 22 fields in Play + Postgres Async . My solution in Scala 2.10 was to break the models into multiple case classes, but I find this solution hard to maintain and extend, and I was hoping I could implement something as described below after switching to Play 2.3.0-RC1 + Scala 2.11.0: package entities case class MyDbEntity( id: String, field1: String, field2: Boolean, field3

With Scala 2.11, we are allowed to have more then 22 fields in a case class right?? case class SomeResponse( var compositeKey: String, var id1: String, var id2: String, var firstName: String, var lastName: String, var email: String, var email2: String, var birth: Long, var gender: String, var phone: Phone, var city: String, var zip: String, var carriage: Boolean, var carriage2: Boolean, var fooLong: Long, var fooLong2: Long, var suspended: Boolean, var foo: Foo, var address: String, var suite: String, var state: String, var instructions: String) implicit val formatSomeResponse = Json.format