I've pushed the branch to github. Although the build is still broke in GH actions, it works locally on:
- derby - h2 (2.3.x), both in-memory and tcp dbs - postgresql (latest) - mariadb (lts) - mysql (lts) The branch is still on JPA 3.1 because I wanted to have a working and green tested baseline after bumps on dependencies, but before starting actual work on impl. The duplicate branch push is due my rebase after the recently merging of pending PRs. Best regards, Paulo ---- Em qua, 02 jul 2025 22:15:42 -0300 Maxim Solodovnik <solomax...@gmail.com> escreveu --- +1 for move on :) from mobile (sorry for typos ;) On Thu, Jul 3, 2025, 03:02 Romain Manni-Bucau < mailto:rmannibu...@gmail.com > wrote: > sounds good to me > > Romain Manni-Bucau > @rmannibucau < https://x.com/rmannibucau > | .NET Blog > < https://dotnetbirdie.github.io/ > | Blog < https://rmannibucau.github.io/ > > | Old > Blog < http://rmannibucau.wordpress.com > | Github > < https://github.com/rmannibucau > | LinkedIn > < https://www.linkedin.com/in/rmannibucau > | Book > < > https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064 > > > > > > Le mer. 2 juil. 2025 à 21:36, Paulo Araújo < > mailto:cris...@vikeo.com.br.invalid > > a > écrit : > > > Hello! > > > > Could we start the work to evolve openjpa to JPA 3.2? > > > > I've made some changes in my branch to push minimum JDK version to 17. > > > > For now, it is just some bumps in dependencies versions of the project, > > some cleanups in violations of checkstyle and removal of deprecated > methods > > (mostly on the SecurityManager front). The build still works, but it > > touches a big chunk of files and the revision would be a nightmare, I > guess. > > > > > > > > I was planning to submit this startup work as a tentative 4.2.0-SNAPSHOT > > version and keep working on the features added in spec (a lot more than > > 3.0-to-3.1). > > > > What do you think about it? > > Best regards, > > > > Paulo >
