Hi Fabian, no real reason I guess, feel free to open a PR
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-performance> Le mar. 7 août 2018 à 13:22, gilbertoca <[email protected]> a écrit : > Hello, Fabian! > > Based on this answer[1] by Romain I think they are targeting the 2.2 spec > and waiting for the release of the Jakarta EE TCKs[2]. > > Regards, > > Gilberto > > [1] > > http://tomee-openejb.979440.n4.nabble.com/Apache-TomEE-7-0-5-and-JPA-2-1-td4684185.html > [2] https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck > > > fabian-a.richter wrote > > Hi, > > > > the OpenJPA team released its JPA 2.1 release at the same time as the > > update for 2.0 (2.4.3) > > > > As TomEE 7 is Java EE 7 based (which includes JPA 2.1 if I am not > > mistaken) why didn’t the 7.0.5 release finally incude the (correct) JPA > > 2.1 compliant relase of OpenJPA? > > > > You guys do maintain the OpenEJB packages as well, don’t you? > > > > What was the reason for still packaging a JPA 2.0 implementation into a > > JPA 2.1 application server? > > > > Thanks and best, > > > > Fabian > > smime.p7s (7K) > > < > http://tomee-openejb.979440.n4.nabble.com/attachment/4684429/0/smime.p7s> > ; > > > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html >
