My Upgrade from Play! Framework 2.0.4 to 2.1.0 went smooth except for these few things

Posted by Brian Porter on February 07, 2013

Today I decided to upgrade from Play Framework 2.0.4 to the newly released 2.1.0.

I followed their helpful guide: http://www.playframework.com/documentation/2.1.0/Migration

Here is a list of the problems I had, and how I solved them:

  1. When it says change the import in the Build.scala to  import play.Project._
Don&#8217;t forget the &#8220;`play.`&#8220;</li> 

  * It says that &#8220;the `mainLang` parameter for the project is not required anymore&#8221; &#8211; but it really means remove it.
  * I also had to Google to figure how to update this dependency: 
        "com.typesafe" %% "play-plugins-mailer" % "2.1-RC2"

  * I also ended up having to update the dependencies for Deadbolt as well to the following: 
        "be.objectify" %% "deadbolt-core" % "2.1-SNAPSHOT",
        "be.objectify" %% "deadbolt-java" % "2.1-SNAPSHOT",</ol> 

Otherwise, follow the instructions &#8211; the rest was pretty straight forward.

I also used a pull request from the <a href="https://github.com/martinp/pvm" onclick="javascript:pageTracker._trackPageview('/outbound/article/github.com');">PVM (Play Version Manager)</a> to download and switch Play Framework Versions.

If you made it this far, you may as well follow me on LinkedIn: Follow Brian Porter

← Previous Post Next Post →