61dd9fce73
In gh-30549 we applied changes to the `DefaultPersistenceUnitManager` to use the `ValidationMode.CALLBACK` to better detect invalid validation setup and enforce bootstrap failures in those cases. Unfortunately, doing so disables the detection of validation annotation on entities during the schema creation phase. This is a known Hibernate issue. This commit reverts this change until HHH-12287 is fixed. Fixes gh-31726
24 lines
935 B
Groovy
24 lines
935 B
Groovy
description = "Spring Object/Relational Mapping"
|
|
|
|
dependencies {
|
|
api(project(":spring-beans"))
|
|
api(project(":spring-core"))
|
|
api(project(":spring-jdbc"))
|
|
api(project(":spring-tx"))
|
|
compileOnly("org.graalvm.sdk:graal-sdk")
|
|
optional(project(":spring-aop"))
|
|
optional(project(":spring-context"))
|
|
optional(project(":spring-web"))
|
|
optional("jakarta.servlet:jakarta.servlet-api")
|
|
optional("org.eclipse.persistence:org.eclipse.persistence.jpa")
|
|
optional("org.hibernate:hibernate-core-jakarta")
|
|
testImplementation(project(":spring-core-test"))
|
|
testImplementation(testFixtures(project(":spring-beans")))
|
|
testImplementation(testFixtures(project(":spring-context")))
|
|
testImplementation(testFixtures(project(":spring-core")))
|
|
testImplementation(testFixtures(project(":spring-web")))
|
|
testImplementation("org.aspectj:aspectjweaver")
|
|
testImplementation("org.hsqldb:hsqldb")
|
|
testRuntimeOnly("jakarta.xml.bind:jakarta.xml.bind-api")
|
|
}
|