Ebean ORM 已从主要 Play 核心中移除，并已作为依赖项引入 Play 2.4。伟大的举动。
但这破坏了现有的代码。遵循 Ebean 的 Play迁移说明后，我收到了几个 JPA 注释错误。经调查，似乎 ebean 正在拉动 JPA 1.0 持久性 API。
[info] | +-org.avaje.ebeanorm:avaje-ebeanorm-agent:4.5.3
[info] | | +-javax.persistence:persistence-api:1.0
[info] | |
[info] | +-org.avaje.ebeanorm:avaje-ebeanorm:4.6.2
[info] | +-com.fasterxml.jackson.core:jackson-core:2.4.1 (evicted by: 2.5.3)
[info] | +-com.fasterxml.jackson.core:jackson-core:2.4.3 (evicted by: 2.5.3)
[info] | +-com.fasterxml.jackson.core:jackson-core:2.5.3
[info] | +-javax.persistence:persistence-api:1.0
[info] | +-org.slf4j:slf4j-api:1.7.12
[info] | +-org.slf4j:slf4j-api:1.7.7 (evicted by: 1.7.12)
在 Play 2.3.9 中，情况并非如此，它在拉我 jpa 2.0
[info] | +-org.avaje.ebeanorm:avaje-ebeanorm-agent:3.2.2
[info] | +-org.avaje.ebeanorm:avaje-ebeanorm:3.3.4
[info] | +-org.hibernate.javax.persistence:hibernate-jpa-2.0-api:1.0.1.Final
[info] |
[info] +-com.typesafe.play:play-java-jdbc_2.11:2.3.9 [S]
[info] | +-com.typesafe.play:play-java_2.11:2.3.9 [S]
[info] | | +-com.google.code.findbugs:jsr305:2.0.3
[info] | | +-com.google.guava:guava:16.0.1
关于排除 JPA 1.0 并依赖 hibernate-jpa-2.0-api 的任何指针？