[
https://issues.apache.org/jira/browse/OPENJPA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080590#comment-18080590
]
ASF subversion and git services commented on OPENJPA-2940:
----------------------------------------------------------
Commit d93cb521480432ca43cb7daeb7c78c4f3fac38d9 in openjpa's branch
refs/heads/OPENJPA-2940 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=d93cb5214 ]
[OPENJPA-2940] Bump docker-compose MariaDB image to 11.8
mariadb:lts now resolves to 11.8 while our compose was pinned to 11.4,
causing drift between local runs and what reviewers / CI pull with the
lts tag. Pin to 11.8 explicitly so TestBatchLimitException and
friends exercise the current LTS behaviour by default.
> 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)
