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:
- When it says change the import in the Build.scala to
import play.Project._Don’t forget the “
play.” - It says that “the
mainLangparameter for the project is not required anymore” — 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",
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:Follow @poornerd
February 8, 2013 at 00:20
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.
February 8, 2013 at 07:01
Thanks for the corrections Fabian — it was late at night when I wrote it
February 27, 2013 at 15:28
Thanks for the tricks, it helped me alot, especially with the mailer plugin problem.
May 14, 2013 at 07:29
Hi Brian, thank you for sharing this, I was just upgrading and this was nice additional info to original migration guide.