I have been having an ugly time with Ebean since I started using Play Framework, which I absolutely love otherwise.
Ebean has just fixed a bug that is affecting me, but it seems that the fix was not picked up during the last deployment of Play which was v2.2.2, which I have updated to.
Is is possible to manually upgrade Ebean in my instance?
EDIT: We brought up the issue with TypeSafe, and James Roper was nice enough to create a compatibility library. Using that, we've been able to successfully use the 3.3.3 version of the Ebean library.
It's as simple as adding this to your Build.scala/sbt file:
libraryDependencies ++= Seq(
"org.avaje.ebeanorm" % "avaje-ebeanorm" % "3.3.3",
"com.typesafe.play" % "play-ebean-33-compat" % "1.0.0"
)
The compatibility library is here: https://github.com/typesafehub/play-ebean-33-compat
ORIGINAL: Late to the party, but I think this is currently not possible, since the Play Ebean Plugin in Play 2.2.3 is incompatible with the Ebean 3.3.x releases.
This issue exists against the Play Framework https://github.com/playframework/playframework/issues/2672. What I've found is that after subsequent recompiles (without cleaning), it will eventually compile and even work. This may lead you to believe that this is not an issue at all. This probably has to do with the older version of the Ebean library getting picked up eventually.
Try to put this on your SBT
dependencyOverrides += "org.avaje.ebeanorm" % "avaje-ebeanorm-agent" % "3.2.2","org.avaje.ebeanorm" % "avaje-ebeanorm" % "3.3.1-RC2"
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With