Hi,
In the next few weeks, we can expect that a final release of Jakarta
Persistence 3.1 SPEC API *may* become available (time permitting :-).
In the mean time there is a staged jakarta.persistence-api-3.1.0-RC2.jar
[1]. Technically, artifacts like jakarta.persistence-api-3.1.0-RC2.jar
could be updated (e.g. like a snapshot) but generally that typically
doesn't happen.
Should we start to build Hibernate ORM 6 with
jakarta.persistence-api-3.1.0-RC2.jar [1] to start making changes for
Persistence 3.1? Or should we wait for the official Persistence 3.1
release?
I would love to hear any feedback on new TCK tests added to the
Persistence 3.1 TCK [2] before Persistence 3.1 final is released so that
we might have time to make any needed corrections in the TCK (instead of
needing to file TCK challenges). The TCK test additions are [3][4][5].
Also worth noting [6] due to a ClassTransformer change.
Scott
[1]
https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/per...
[2]
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/j...
[3]
https://github.com/eclipse-ee4j/jakartaee-tck/pull/793 UUID entity
[4]
https://github.com/eclipse-ee4j/jakartaee-tck/pull/775 JPQL EXTRACT
[5]
https://github.com/eclipse-ee4j/jakartaee-tck/pull/759 EntityManager
+ EntityManagerFactory are AutoCloseable
[6]
https://github.com/eclipse-ee4j/jakartaee-tck/pull/805
ClassTransformer#transform now throws TransformerException