升级到Play框架后的JPA依赖项问题2.4

Question

Ebean ORM已从Play主内核中提取出来，并已作为Play 2.4中的依赖项引入。伟大的举措。

但这是打破现有的代码。在遵循Ebean的Play migration说明之后，我收到了几个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) 

凡在播放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和依赖休眠-JPA-2.0-API？

Answer 1

您可以从ebean依赖关系中排除persistence-api。

像

("org.avaje.ebeanorm" % "avaje-ebeanorm" % "4.6.2").exclude("javax.persistence","persistence-api")