No strong preference, guess we can do a v5 if we impl the spec but i dont see it being soon since we are late on 2.1 already.
Le ven. 20 oct. 2023 à 14:29, Richard Zowalla <rich...@zowalla.com> a écrit : > From my side: I would love to have a stable Jakarta-ready artifact (to > avoid building against a SNAPSHOT), so I can get the OWB4 branch into > TomEE main and start further work on the TCK frontlines / do a > milestone release. > > JPA-3.1 foR EE10 would be (according to [1]): > > - EntityManagerFactory and EntityManager interfaces extend > java.lang.AutoCloseable interface > - Fixes ClassTransformer.transform to throw Persistence API specific > exception > - Adds support for java.util.UUID and GenerationType.UUID > - Adds CEILING, EXP, FLOOR, LN, POWER, ROUND, and SIGN numeric > functions to Jakarta Persistence QL and ceiling(), exp(), floor(), > ln(), power(), round(), and sign() to Criteria API > - Adds LOCAL DATE, LOCAL DATETIME, and LOCAL TIME functions to Jakarta > Persistence QL and corresponding localDate(), localDateTime(), and > localTime() to Criteria API > - Adds EXTRACT function to Jakarta Persistence QL > - Adds support for Expressions as conditions in Criteria CASE > expressions > - Adds missing definition of single_valued_embeddable_object_field in - > Jakarta Persistence QL BNF > - Clarifies mixing types of query input parameters > - Clarifies definition of the Basic type > - Clarifies the order of parameters in the LOCATE function > - Clarifies SqlResultSetMapping with multiple EntityResults and > conflicting aliases > > So maybe 4.0.0 for JPA 3.0 and 4.1.0 for JPA 3.1 ? ;-) > > Gruß > Richard > > > [1] https://jakarta.ee/specifications/persistence/3.1/ > > > Am Freitag, dem 20.10.2023 um 14:16 +0200 schrieb Mark Struberg: > > The major question which is still left for me: this is now Jakarta > > JPA-3.0. There got changes made to the API made in JPA-4.0 Do we like > > to tackle those as well? Or do we make a release with JPA-3.0 level > > and only later do a 4.0? Or invest this bit of work and work towards > > a 4.0 EE10 immediately? > > > > LieGrue, > > strub > > > > > > > Am 20.10.2023 um 09:06 schrieb Richard Zowalla > > > <rich...@zowalla.com>: > > > > > > I am fine with it. I had a quick chat with Mark and after he fixed > > > a > > > regression in the OPENJPA SNAPSHOT found while building TomEE, he > > > was > > > also like "let's do a release". > > > > > > So maybe just a final and minors, if we find bugs / build new > > > features? > > > > > > Gruß > > > Richard > > > > > > Am Donnerstag, dem 19.10.2023 um 19:01 +0200 schrieb Romain Manni- > > > Bucau: > > > > Guess we can do a final, we never fully implemented the spec (for > > > > good and > > > > bad reasons) so if Mark gives his go on the work he did on the > > > > bytecode I'm > > > > for a final. > > > > > > > > Romain Manni-Bucau > > > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > > > <https://rmannibucau.metawerx.net/> | Old Blog > > > > <http://rmannibucau.wordpress.com> | Github > > > > <https://github.com/rmannibucau> | > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > > > > < > > > > > https://www.packtpub.com/application-development/java-ee-8-high-perfor > > > > mance> > > > > > > > > > > > > Le jeu. 19 oct. 2023 à 18:54, Richard Zowalla <r...@apache.org> a > > > > écrit : > > > > > > > > > Hi all, > > > > > > > > > > can we do a a milestone release (4.0.0-M1 or similar) of > > > > > OpenJPA ? > > > > > > > > > > I would like to build TomEE 10.x against a stable version of > > > > > OpenJPA, so we might be able to do a milestone/alpha release of > > > > > a > > > > > TomEE 10 since the normal build is looking good. > > > > > > > > > > Gruß > > > > > Richard > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
