[
https://issues.apache.org/jira/browse/OPENJPA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080857#comment-18080857
]
Paulo Cristovão de Araújo Silva Filho commented on OPENJPA-2940:
----------------------------------------------------------------
Hi, folks!
After [~rzo1] contributions, it seems all JPA 3.2 features are present in
OPENJPA-2940 branch. Right now, the build of github action (derbydb) passes,
and the ci-build (h2-2, openjpa-JPA-3.2 #15) also passes. I'm running locally
the builds for postgresql (18), mariadb (lts) and mysql (lts), but previous
runs also passed.
Richard's contributions were aided by Claude AI, with my revision afterwards. I
still suspect the need of commits fbae29f (and the dependent cf0166f) because
OID fields support should be handled by postgresql JDBC driver, but Richards
TCK tests showed errors. It would be great if some of you with more project
experience could independently test it.
As Richard reported, JPA 3.2 TCK is passing, and, provided the PR I'll open
later is accepted, OpenJPA will have the 3.0 missing features also.
> Implement Jakarta Persistence 3.2
> ---------------------------------
>
> Key: OPENJPA-2940
> URL: https://issues.apache.org/jira/browse/OPENJPA-2940
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Paulo Cristovão de Araújo Silva Filho
> Priority: Major
> Attachments: image-2026-03-28-14-55-26-463.png
>
>
> Implement Jakarta Persistence API 3.2 as prescribed by
> [specification|https://jakarta.ee/specifications/persistence/3.2/] and
> required by Jakarta EE 11.
> This change requires JDK17 or higher compatibility and needs considerable
> checks.
> I've already pushed a branch (WIP) without the proper API bump, focusing on
> updating dependencies while keeping the project passing its current tests at
> least in default profile.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
