I ran into the same problem. The question here is that play-java-jpa artifact (the javaJpa key in the build.sbt file) depends on another version of spec (version 2.0 -> "org.hibernate.javax.persistence" % "hibernate-jpa-2.0-api" % "1.0.1.Final")
.
When you added hibernate-entitymanager 4.3, this led to the newer specification (2.1) and another factory provider for entitymanager. Basically, you have both bans in the class path as transitive dependencies.
Modify the build.sbt file this way and it will temporarily fix your problem until playback releases a new version of the jpa plugin for a newer api dependency.
libraryDependencies ++= Seq( javaJdbc, javaJpa.exclude("org.hibernate.javax.persistence", "hibernate-jpa-2.0-api"), "org.hibernate" % "hibernate-entitymanager" % "4.3.0.Final" )
This is for play 2.2.x
There were some differences in build files in previous versions.
hcura Dec 27 '13 at 12:37 2013-12-27 12:37
source share