my thoughts on programming and other nerdy stuff

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


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’t forget the “play.

  2. It says that “the mainLang parameter for the project is not required anymore” – but it really means remove it.
  3. I also had to Google to figure how to update this dependency:
    "com.typesafe" %% "play-plugins-mailer" % "2.1-RC2"
  4. 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",

Otherwise, follow the instructions – the rest was pretty straight forward.

I also used a pull request from the PVM (Play Version Manager) to download and switch Play Framework Versions.

If you have read this far, you may as well follow me on Twitter:

Author: poornerd

Tech­nol­o­gist, Entre­pre­neur, Vision­ary, Pro­gram­mer :: Grad­u­ated from USC (Uni­ver­sity of South­ern Cal­i­for­nia) with a degree in Com­puter Sci­ence. After 10+ years of free­lance con­sult­ing and pro­gram­ming, he co-founded Site­Force AG eBusi­ness Solu­tions in 1999 in Munich (München), Ger­many.


  1. You mean 2.1.0, not “newly released 2.0.1”.
    And 2 more minur text corrections:
    And “for get” => “forget”
    “how how” => “out how”

    Thanks for paving the way… I’ll try to upgrade mine soon.

  2. Thanks for the tricks, it helped me alot, especially with the mailer plugin problem.

  3. Hi Brian, thank you for sharing this, I was just upgrading and this was nice additional info to original migration guide.

  4. Since your blog came up first on google again 😉 I find this worth adding:
    1) the mailer plugin is now available as 2.1.0 (no “2.1-RC2” anymore).
    2) another undocumented incompatibility I came across: instead of new Html(myString) it’s now Html.apply(myString)

Leave a Reply

Required fields are marked *.